Applications And Skills For An Autonomous Unmanned Aerial Vehicle

ABSTRACT

A technique is described for developing and using applications and skills with an autonomous vehicle. In an example embodiment, a development platform is provided that enables access to a developer console for developing software modules for use with an autonomous vehicle. Using the developer console, a developer user can specify instructions for causing an autonomous vehicle to perform one or more operations. For example, to control the behavior of an autonomous vehicle, the instructions can cause an executing computer system at the autonomous vehicle to generate calls to an application programming interface (API) associated with an autonomous navigation system of autonomous vehicle. Such calls to the API can be configured to adjust a parameter of a behavioral objective associated with a trajectory generation process performed by the autonomous navigation system that controls the behavior of the autonomous vehicle. The instructions specified by the developer can be packaged as a software module that can be deployed for use at autonomous vehicle.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. patent application Ser. No. 16/559,512, titled “APPLICATIONS AND SKILLS FOR AN AUTONOMOUS UNMANNED AERIAL VEHICLE,” filed Sep. 3, 2019; which is entitled to the benefit and/or right of priority of U.S. Provisional Application No. 62/726,888, titled “APPLICATIONS AND SKILLS FOR AN AUTONOMOUS UNMANNED AERIAL VEHICLE,” filed Sep. 4, 2018; the contents of each of which are hereby incorporated by reference in their entirety for all purposes. This application is therefore entitled to a priority date of Sep. 4, 2018.

TECHNICAL FIELD

The present disclosure generally relates to autonomous vehicle technology.

BACKGROUND

Unmanned aerial vehicles (UAV) are increasingly being used for a variety of purposes such as capturing images (including video) from the air. A number of UAV systems are currently available that provide for image and video capture and remote control from a device on the ground. However, currently available systems require piloting using direct control of the UAV similar to other fixed wing or rotor craft. In other words, control by directly adjusting the pitch, roll, yaw, and power of the UAV, for example, using common control inputs such as a joystick and throttle control. While effective to a degree, such control systems require expertise on the part of the remote pilot and are prone to crashes caused by pilot error.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A shows an example configuration of an autonomous vehicle in the form of an unmanned aerial vehicle (UAV) within which certain techniques described herein may be applied;

FIG. 1B shows another configuration of an autonomous vehicle in the form of a fixed-wing UAV within which certain techniques described herein may be applied;

FIG. 2 shows a block diagram illustrating an example navigation system of a UAV;

FIG. 3 shows a block diagram illustrating an example configuration for inputting objectives to the navigation system of FIG. 2 via an application programming interface (API);

FIG. 4 shows a diagram illustrating an example world-relative objective;

FIG. 5 shows a diagram illustrating an example vehicle-relative objective;

FIGS. 6A-6B show diagrams illustrating an example subject-relative objective;

FIG. 7 shows a diagram illustrating an example subject-relative objective to maintain line-of-sight with a tracked subject;

FIG. 8 shows a diagram illustrating an example image-relative objective;

FIG. 9 shows a diagram illustrating an example objective to avoid backlighting;

FIG. 10 shows a diagram illustrating an example objective to maintain scene saliency;

FIG. 11 shows a diagram illustrating an example objective to avoid collisions with other objects;

FIG. 12 shows a block diagram illustrating multi-objective optimization-based motion planning based on objective inputs received via an API;

FIG. 13 shows a block diagram illustrating certain parameters of an objective;

FIG. 14 shows a block diagram illustrating components of example skills in an example application;

FIG. 15 shows a diagram illustrating an example implementation of an application including multiple skills in a system involving a UAV and an associated mobile device;

FIG. 16 shows a flow diagram of an example process for controlling an autonomous vehicle using one or more skills;

FIG. 17 shows a flow diagram of another example process for controlling an autonomous vehicle using one or more skills;

FIG. 18 shows a diagram illustrating an example implementation of a platform for developing and/or distributing applications and skills;

FIG. 19 shows a flow diagram of an example process for generating skills and/or applications;

FIG. 20 shows a diagram illustrating an example implementation of a global simulation environment;

FIG. 21 shows a flow diagram illustrating an example scenario for uploading a custom machine learning model to extend the functionality of a navigation system of a UAV;

FIG. 22 shows a flow diagram illustrating an example process by which outputs from custom machine learning models are accessed by developer-created skills;

FIG. 23 shows a diagram that illustrates image-based training data for various tasks used to train machine-learning models;

FIG. 24 shows s a flow diagram illustrating an example scenario for uploading training data to train a custom machine learning model to extend the functionality of the underlying navigation system of a UAV;

FIG. 25 shows an example of a visual output displayed via a mobile device in the form of a tablet display device;

FIG. 26 shows an example view of a physical environment as presented at a display of an augmented reality device;

FIG. 27 shows a series of screen captures illustrating how graphical user interface (GUI) features associated with a developer-created skill can be integrated into an application configured to control a UAV;

FIG. 28 shows an example visual output that includes 3D waypoint objects displayed as augmentations;

FIG. 29 shows a diagram of an example localization system with which at least some operations described in this disclosure can be implemented;

FIG. 30 shows a diagram illustrating the concept of visual odometry based on captured images;

FIG. 31 shows an example view of a three-dimensional (3D) occupancy map of a physical environment;

FIG. 32 shows an example image captured by a UAV in flight through a physical environment with associated visualizations of data regarding tracked objects based on processing of the captured image;

FIG. 33 shows a diagram illustrating an example process for estimating a trajectory of an object based on multiple images captured by a UAV;

FIG. 34 shows a diagrammatic representation of an example spatiotemporal factor graph;

FIG. 35 shows a diagram that illustrates an example process of generating an intelligent initial estimate for where a tracked object will appear in a subsequently captured image;

FIG. 36 shows a visualization representative of a dense per-pixel segmentation of a captured image;

FIG. 37 shows a visualization representative of an instance segmentation of a captured image;

FIG. 38 shows a block diagram of an example UAV system including various functional system components with which at least some operations described in this disclosure can be implemented; and

FIG. 39 shows a block diagram of an example of a processing system in which at least some operations described in this disclosure can be implemented.

DETAILED DESCRIPTION Overview

To alleviate the need for direct pilot control, UAVs used as aerial image capture platforms can be configured for autonomous operation. Achieving autonomous flight in a safe and intelligent manner involves a complex hierarchy of physics, control systems, scene understanding, and motion planning. Recent improvements in autonomous vehicle technology have generated significant interest from developers to be able to create niche-specific applications that leverage the underlying complexity and power of autonomous vehicle systems. However, the complex nature of autonomous vehicle technology, which makes it so powerful, also creates a high barrier of entry for such application developers seeking to develop such niche applications.

To address such challenges, a development platform is introduced that includes, for example, a set of application programming interfaces (APIs), software development kits (SDKs), and other software development tools that enable software developers to build on and leverage the underlying complexity of an autonomous navigation system. In some embodiments, the described development platform hides the underlying complexity of an autonomous navigations system by supporting development of applications that can control an autonomous vehicle such as a UAV by specifying a collection of intuitive, high-level behavioral intentions also referred to herein “behavioral objectives” or simply as “objectives.”

In some embodiments, using the development platform, developers can create what are referred to herein as “skills” that comprise, for example, instructions and/or other digital assets (e.g., images, video, digital models, visual augmentations, etc.) configured to modify objective inputs to the underlying autonomous navigation system, thereby controlling vehicle behavior during actual flight, during simulated flight, as well as pre-flight and post-flight behavior. In some embodiments, skills and or applications may be implemented as software modules that include the instructions and/or other digital assets. In some embodiments, skills can also be applied to modify outputs to a user, for example via user interface at a connected device. For example, a developer-created skill may change and adjust the type of data collected during a flight (image stills vs video, frame rate, etc.), change and adjust objective inputs to the navigation engine during flight, perform customized post-processing on received data after landing, etc.

As will be described, objectives utilized to control an autonomous vehicle are exposed through one or more API. Applications or “skills” can be developed using SDKs and APIs, shared with other users via an online storefront, downloaded and executed by other users using other UAVs, tested in an online simulation environment, and/or utilized to improve operation of the autonomous control systems. In an example embodiment, the development platform exposes a Mobile SDK, and on-board Skills SDK, and a developer console. The Mobile SDK allows developers to build their own applications (e.g., mobile apps) that are configured to control the operation of an autonomous vehicle such as a UAV. The Skills SDK allows developers to write their own ‘skills’ that run on the autonomous vehicle during flight and manipulate the high-level autonomous behavior of the vehicle. The developer console is an application (e.g., a web app) used by developers to manage the skills they have created (e.g., invite users, deploy new code, etc.), test developed skills in simulation environments (e.g., a rendered three-dimensional (3D) environment with a physics engine representing the actual behavior of the autonomous vehicle while running the developers' skill).

Example Implementation of an Autonomous Vehicle

FIG. 1A shows an example configuration of a UAV 100 within which certain techniques described herein may be applied. As shown in FIG. 1A, UAV 100 may be configured as a rotor-based aircraft (e.g., a “quadcopter”). The example UAV 100 includes propulsion and control actuators 110 (e.g., powered rotors or aerodynamic control surfaces) for maintaining controlled flight, various sensors for automated navigation and flight control 112, and one or more image capture devices 114 and 115 for capturing images of the surrounding physical environment while in flight. “Images,” in this context, include both still images and capture video. Although not shown in FIG. 1A, UAV 100 may also include other sensors (e.g., for capturing audio) and systems for communicating with other devices (e.g., a mobile device 104) via a wireless communication channel 116.

In the example depicted in FIG. 1A, the image capture devices 114 and/or 115 are depicted capturing an object 102 in the physical environment that happens to be a person. In some cases, the image capture devices may be configured to capture images for display to users (e.g., as an aerial video platform) and/or, as described above, may also be configured for capturing images for use in autonomous navigation. In other words, the UAV 100 may autonomously (i.e., without direct human control) navigate the physical environment, for example, by processing images captured by any one or more image capture devices. While in autonomous flight, UAV 100 can also capture images using any one or more image capture devices that can be displayed in real time and or recorded for later display at other devices (e.g., mobile device 104).

FIG. 1A shows an example configuration of a UAV 100 with multiple image capture devices configured for different purposes. In the example configuration shown in FIG. 1A, the UAV 100 includes multiple image capture devices 114 arranged about a perimeter of the UAV 100. The image capture devices 114 may be configured to capture images for use by a visual navigation system in guiding autonomous flight by the UAV 100 and/or a tracking system for tracking other objects in the physical environment (e.g., as described with respect to FIG. 2 ). Specifically, the example configuration of UAV 100 depicted in FIG. 1A includes an array of multiple stereoscopic image capture devices 114 placed around a perimeter of the UAV 100 so as to provide stereoscopic image capture up to a full 360 degrees around the UAV 100.

In addition to the array of image capture devices 114, the UAV 100 depicted in FIG. 1A also includes another image capture device 115 configured to capture images that are to be displayed but not necessarily used for navigation. In some embodiments, the image capture device 115 may be similar to the image capture devices 114 except in how captured images are utilized. However, in other embodiments, the image capture devices 115 and 114 may be configured differently to suit their respective roles.

In many cases, it is generally preferable to capture images that are intended to be viewed at as high a resolution as possible given certain hardware and software constraints. On the other hand, if used for visual navigation and/or object tracking, lower resolution images may be preferable in certain contexts to reduce processing load and provide more robust motion planning capabilities. Accordingly, in some embodiments, the image capture device 115 may be configured to capture relatively high resolution (e.g., 3840×2160) color images while the image capture devices 114 may be configured to capture relatively low resolution (e.g., 320×240) grayscale images.

The UAV 100 can be configured to track one or more objects such as a human subject 102 through the physical environment based on images received via the image capture devices 114 and/or 115. Further the UAV 100 can be configured to track image capture of such objects, for example, for filming purposes. In some embodiments, the image capture device 115 is coupled to the body of the UAV 100 via an adjustable mechanism that allows for one or more degrees of freedom of motion relative to a body of the UAV 100. The UAV 100 may be configured to automatically adjust an orientation of the image capture device 115 so as to track image capture of an object (e.g., human subject 102) as both the UAV 100 and object are in motion through the physical environment. In some embodiments, this adjustable mechanism may include a mechanical gimbal mechanism that rotates an attached image capture device about one or more axes. In some embodiments, the gimbal mechanism may be configured as a hybrid mechanical-digital gimbal system coupling the image capture device 115 to the body of the UAV 100. In a hybrid mechanical-digital gimbal system, orientation of the image capture device 115 about one or more axes may be adjusted by mechanical means, while orientation about other axes may be adjusted by digital means. For example, a mechanical gimbal mechanism may handle adjustments in the pitch of the image capture device 115, while adjustments in the roll and yaw are accomplished digitally by transforming (e.g., rotating, panning, etc.) the captured images so as to effectively provide at least three degrees of freedom in the motion of the image capture device 115 relative to the UAV 100.

FIG. 2 is a block diagram that illustrates an example navigation system 120 that may be implemented as part of the example UAV 100 described with respect to FIG. 1A. The navigation system 120 may include any combination of hardware and/or software. For example, in some embodiments, the navigation system 120 and associated subsystems, may be implemented as instructions stored in memory and executable by one or more processors.

As shown in FIG. 2 , the example navigation system 120 includes a motion planning system 130 for autonomously maneuvering the UAV 100 through a physical environment and a tracking system 140 for tracking one or more objects in the physical environment. The tracking subsystem 140 may include one or more subsystems such as an object detection subsystem, an instance segmentation subsystem, an identity recognition subsystem, and any other subsystems (all not shown). The purposes of such subsystems are described in more detail later. Note that the arrangement of systems shown in FIG. 2 is an example provided for illustrative purposes and is not to be construed as limiting. For example, in some embodiments, the tracking system 140 may be completely separate from the navigation system 120. Further, the subsystems making up the navigation system 120 may not be logically separated as shown in FIG. 2 .

In some embodiments, the motion planning system 130, operating separately or in conjunction with the tracking system 140, is configured to generate a planned trajectory through a three-dimensional (3D) space of a physical environment based, for example, on images received from image capture devices 114 and/or 115, data from other sensors 112 (e.g., IMU, GPS, proximity sensors, etc.), one or more control inputs 170 from external sources (e.g., from a remote user, navigation application, etc.), and/or one or more specified navigation objectives. As will be described in more detail, the control inputs 170 may include calls to an API associated with navigation system 120. For example, API calls may be made by an application for setting one or more navigation objectives as part of the motion planning process. Navigation objectives will be described in more detail later, but may include, for example, avoiding collision with other objects and/or maneuvering to follow a particular object (e.g., an object tracked by tracking system 140). In some embodiments, the generated planned trajectory is continuously or continually (i.e., at regular or irregular intervals) updated based on new perception inputs (e.g., newly captured images) and/or new control inputs 170 received as the UAV 100 autonomously navigates the physical environment.

In some embodiments, the navigation system 120 may generate control commands configured to cause the UAV 100 to maneuver along the planned trajectory generated by the motion planning system 130. For example, the control commands may be configured to control one or more control actuators 110 (e.g., rotors and/or control surfaces) to cause the UAV 100 to maneuver along the planned 3D trajectory. Alternatively, a planned trajectory generated by the motion planning system 120 may be output to a separate flight controller system 160 that is configured to process trajectory information and generate appropriate control commands configured to control the one or more control actuators 110.

The tracking system 140, operating separately or in conjunction with the motion planning system 130, may be configured to track one or more objects in the physical environment based, for example, on images received from image capture devices 114 and/or 115, data from other sensors 112 (e.g., IMU, GPS, proximity sensors, etc.), one or more control inputs 170 from external sources (e.g., from a remote user, navigation application, etc.), and/or one or more specified tracking objectives. Again, in some embodiments, tracking objectives may be set based on API calls from an application, for example, based on user inputs received through the application. Tracking objects will be described in more detail later, but may include, for example, a designation by a user to track a particular detected object in the physical environment or a standing objective to track objects of a particular classification (e.g., people).

As alluded to above, the tracking system 140 may communicate with the motion planning system 130, for example, to maneuver the UAV 100 based on measured, estimated, and/or predicted positions, orientations, and/or trajectories of objects in the physical environment. For example, the tracking system 140 may communicate a navigation objective to the motion planning system 130 to maintain a particular separation distance to a tracked object that is in motion.

In some embodiments, the tracking system 140, operating separately or in conjunction with the motion planner 130, is further configured to generate control commands configured to cause one or more stabilization/tracking devices 152 to adjust an orientation and/or position of any image capture devices 114/115 relative to the body of the UAV 100 based on the motion of the UAV 100 and/or the tracking of one or more objects. Such stabilization/tracking devices 152 may include a mechanical gimbal or a hybrid digital-mechanical gimbal, as previously described. For example, while tracking an object in motion relative to the UAV 100, the tracking system 140 may generate control commands configured to adjust an orientation of an image capture device 115 so as to keep the tracked object centered in the field of view (FOV) of the image capture device 115 while the UAV 100 is in motion. Similarly, the tracking system 140 may generate commands or output data to a digital image processor (e.g., that is part of a hybrid digital-mechanical gimbal) to transform images captured by the image capture device 115 to keep the tracked object centered in the FOV of the image capture device 115 while the UAV 100 is in motion. The image capture devices 114/115 and associated stabilization/tracking devices 152 are collectively depicted in FIG. 2 as an image capture system 150.

The UAV 100 shown in FIG. 1A and the associated navigation system 120 shown in FIG. 2 are examples provided for illustrative purposes. A UAV 100 in accordance with the present teachings may include more or fewer components than are shown. Further, the example UAV 100 depicted in FIG. 1A and associated navigation system 120 depicted in FIG. 2 may include or be part of one or more of the components of the example UAV system 2600 described with respect to FIG. 26 and/or the example computer processing system 2700 described with respect to FIG. 27 . For example, the aforementioned navigation system 120 and associated tracking system 140 may include or be part of the UAV system 2600 and/or processing system 2700.

While the introduced technique for objective-based control of an autonomous vehicle using an API is described in the context of an aerial vehicle such as the UAV 100 depicted in FIG. 1A, such a technique is not limited to this context. The described technique may similarly be applied to guide navigation and image capture by other types of vehicles (e.g., fixed-wing aircraft, automobiles, watercraft, etc.), hand-held image capture devices (e.g., mobile devices with integrated cameras), or to stationary image capture devices (e.g., building mounted security cameras). For example, FIG. 1B shows an example of a fixed-wing UAV 100 b. Similar to the UAV 100 described with respect to FIG. 1A, the fixed-wing UAV 100 b shown in FIG. 1B may include multiple image capture devices 114 b arranged about a perimeter of the UAV 100 b configured to capture images for use by a visual navigation system in guiding autonomous flight by the UAV 100 b. The example fixed-wing UAV 100 b may also include a subject image capture device 115 b configured to capture images (e.g., of subject 102) that are to be displayed but not necessarily used for navigation. For simplicity, embodiments of the introduced technique are described herein with reference to the UAV 100 of FIG. 1A; however, a person having ordinary skill in the art will recognize that the introduced technique can be similarly applied using the fixed-wing UAV 100 b of FIG. 1B.

Objective-Based Control of an Autonomous Vehicle Using an API

The complex processing by a navigation system 120 to affect the autonomous behavior of a UAV 100 can be abstracted into one or more behavioral objectives. A “behavioral objective” or “objective” in this context generally refers to any sort of defined goal or target configured to guide an autonomous response by the UAV 100. For example, objectives may be configured to approximate certain intentions of a human pilot. FIGS. 4-11 will describe some example “objectives” within the meaning of this term as used herein. It shall be appreciated that the example objectives described with respect to FIGS. 4-11 are provided for illustrative purposes and are not to be construed as limiting. A system in accordance with the present discloser may be based on fewer or more objectives than are described.

The underlying processes performed by a navigation system 120 for causing a UAV 100 to autonomously maneuver through an environment and/or perform image capture can be exposed through an API. For example, FIG. 3 shows a diagram of navigation system 120 including a motion planning component 130 and tracking component 140, for example, as described with respect to FIG. 2 . As previously discussed with respect to FIG. 2 , the navigation system 120 may generate control outputs 302 such as a planned trajectory, specific control commands, and or image capture outputs based on perception inputs received from sensors (e.g., image capture devices 114/115 and/or other sensors 112) as well as one or more control inputs 170. In the context of the diagram of FIG. 3 , such control inputs may be in the form of calls to an API 300 defining parameters of one or more objectives 1 through N.

As will be described in more detail, the API 300 may be configured as a public facing API that may be utilized by a developer to create applications configured to enable certain user interactions with the UAV 100 without specific knowledge of the underlying processes of the navigation system 120 that enable autonomous behavior by the UAV 100. In some cases, the developer creating such applications may be a “second-party” or “third-party” developer, meaning that the developer may be an entity other than the original developer of the navigation system 120 (or one or more internal components of the navigation system 120).

World-Relative Objectives

In some embodiments, an objective may be expressed in terms relative to the physical environment in which the UAV 100 resides. Such objectives are referred to herein as “world-relative” objectives. An example of a world-relative navigation objective may include maneuvering the UAV to a specific location in the physical environment. Similarly, a “world-relative” image capture objective may include positioning the UAV 100 and an associated image capture device 115 so as to capture a specific location in the physical environment.

FIG. 4 shows a view of a map 402 of a physical environment. A specific location in the physical environment is indicated at marker 404. In this example, the location may be defined based on a global positioning coordinate (e.g., latitude, longitude), however other types of location indicators may similarly be applied. For example, locations in the physical environment may similarly be defined based on a local coordinate system (e.g., a grid coordinate for a particular city), position/orientation coordinate relative to a takeoff point of the UAV 100 (i.e., a navigation coordinate), other types of location identifiers (e.g., a mailing address), a name of a point of interest (e.g., the Golden Gate Bridge) at a known location, and the like.

A target of a world-relative objective may be expressed based on any of the above-mentioned types of location indicators. For example, a world-relative objective in the form of a GPS coordinate (e.g., 37.40, −122.16) may be input into the navigation system 120 of UAV 100 (e.g., in the form of a call to API 300) to cause the UAV 100 to autonomously maneuver through the physical environment to the designated location and/or direct image capture at the designated location. Note that FIG. 4 shows an indirect path (as indicated by the dotted line) between a current position of the UAV 100 and the location designated by the world-relative objective. Such an indirect path may be based on a planned trajectory generated by a motion planning component 130 of the navigation system 120 to autonomously maneuver the UAV 100 to the designated location 404 while satisfying other objectives such as avoiding obstacles, maintaining visual contact with a subject, etc.

World-relative objectives are described above as being defined based on locations in the physical environment, however they may similarly include other defining parameters such as relative motion (e.g., ground velocity or air velocity), altitude (expressed as a value above mean sea (MSL), above ground level (AGL), etc.), a separation distance to certain objects in the physical environment (e.g., lateral distance to a vertical surface such as a wall), etc. For example, a particular world-relative objective that incorporates multiple defined targets may be semantically expressed as “fly to grid coordinate 37.40, −122.16 while maintaining a velocity of 30 miles per hour and an altitude of at least 1000 AGL.” Similarly, this objective may be expressed as three independent world-relative objectives. As will be described, world-relative objective(s) may be provided as inputs (e.g., in the form of calls to API 300) to the navigation system 120 of the UAV 100 to cause the UAV 100 to autonomously maneuver in a manner that attempts to meet the objective(s) while taking into account other objectives (e.g., avoiding collision with other objects).

Vehicle-Relative Objectives

In some embodiments, an objective may be expressed in terms relative to the vehicle itself (e.g., UAV 100). For example, a vehicle-relative objective may include a target to move forward, backward, left, right, up, down, and/or rotate about one or more axes (e.g., yaw, pitch, roll, etc.) at some defined speed or acceleration (angular speed or acceleration in the case of rotation objectives). Similarly, a vehicle-relative objective may include a target to adjust the position and/or orientation of an image capture device 115 relative to the body of the UAV 100, for example, through the use of a gimbal mechanism.

Vehicle-relative objectives may be defined based on a vehicle-relative coordinate system. For example, FIG. 5 depicts a representative view of an example UAV 100 and a multi-dimensional coordinate system 502 upon which lateral motion (e.g., along X, Y, and Z axes) and rotational motion (e.g., about the X, Y, and Z axes) can be defined. Similar coordinate system may be defined relative to the image capture device 115 for defining image capture objectives.

As an illustrative example, a vehicle-relative objective may be semantically expressed as “move forward (e.g., along the Y axis) at a constant ground speed of 3 miles per hour.” As with the world-relative objectives described above, vehicle-relative objective(s) may be provided as inputs (e.g., in the form of calls to API 300) to the navigation system 120 of the UAV 100 to cause the UAV 100 to autonomously maneuver in a manner that attempts to meet the objective(s) while taking into account other objectives (e.g., avoiding collision with other objects).

Subject-Relative Objectives

In some embodiments, an objective may be expressed in terms relative to some other physical object (i.e., a subject) in the physical environment. The “subject” in this context may include any type of object such as a person, an animal, a vehicle, a building, a landscape feature, or any other static or dynamic physical objects present in the physical environment. For example, a subject-relative navigation objective may include a target to move to and/or maintain a particular position and/or orientation relative to a tracked subject in the physical environment. Similarly, a subject-relative image capture objective to capture maneuver so as to capture images of the tracked subject in the physical environment.

Subject-relative objectives may be defined, for example, in position/orientation terms based on values for an azimuth, elevation, range, height, azimuth rate between the vehicle and the tracked subject. For example, FIGS. 6A-6B show side view and a top view (respectively) that illustrate how relative positioning between a UAV 100 and a tracked subject (in this case a human subject 102) can be defined in terms of an elevation angle θ₁, an azimuth angle θ2, and a range value.

Subject-relative objectives may also include targets that are defined based on a semantic understanding of physical environment that the UAV 100 and subject occupy. For example, a subject-relative objective may include a target to maintain a clear line of sight between the UV 100 and the tracked subject. FIG. 7 depicts an example scenario involving a UAV 100 in flight over a physical environment 720 while capturing images of a human subject 102. As shown in FIG. 7 , at a current time, human subject 102 is located on an opposite side of object 730 from UAV 100; however, as indicated by dotted line 710, a view of human subject 102 from an image capture device onboard UAV 100 is not occluded by object 730. If the human subject 102 moves to a different position behind the object 730, the view of the human subject 102 from the image capture device onboard the UAV 100 may be occluded, as indicated by dotted line 712. Accordingly, to satisfy a subject-relative objective to maintain line of sight, a navigation system 120 may cause the UAV 100 to maneuver (e.g., along trajectory 706 or 704) to a different position such that the view of the human subject 102 is no longer occluded.

Certain techniques for tracking subjects in the physical environment are described later with respect to FIGS. 32-37 ; however, in some embodiments, a motion planning system 130 may employ a specific technique described below in order to satisfy a subject-relative objective to maintain line of sight.

Consider again the scenario depicted in FIG. 7 . Based on a predicted trajectory of human subject 102 (as indicated by arrow 716), and measured or estimated positions of the UAV 100 and object 730, a navigation system 120 may determine that the view of the human subject 102 may become occluded by the object 730 (assuming UAV 100 remains stationary) as indicated by the obstructed line of sight line 712. Based on this predicted future state and a standing objective to maintain line of sight with subject 102, the navigation system 120 may generate outputs (e.g., a predicted trajectory and/or control commands) configured to cause the UAV 100 to maneuver to the UAV 100 to satisfy the subject-relative objective. Here, the generated output may be configured to cause UAV 100 to maneuver along a flight path 706 to keep the view of human subject 102 unobstructed. Note that in this example, simply avoiding a collision with object 730 may not be sufficient to satisfy the objective. For example, if the generated output causes the UAV 100 to maneuver along alternative flight path 704 instead of 706, its view of human subject 102 will become momentarily obstructed by object 730, thereby failing the objective.

The process applied by the motion planning system 130 to maneuver the UAV 100 along trajectory 706 instead of 704 in order to satisfy a line of sight objective may be based on a virtual line of sight in a computer-generated 3D model of the physical environment. As will be described the measured, estimated, and/or predicted motions of UAV 100 and one or more tracked subjects may be based on localization within a computer-generated 3D model representative of the physical environment. The navigation system 120 may then define a virtual line connecting virtual representations of the positions of the UAV 100 and subject 102 in the 3D model. Accordingly, a subject-relative objective to maintain line of sight can be interpreted with the navigation system 120 as an objective to maneuver the UAV 100 such that the virtual line of sight line does not intersect with a virtual representation of another physical object. This criterion may be specified with a certain level of tolerance (i.e., dead zone) to account for objects in motion. In other words, if UAV 100 and/or subject 102 are both in motion, it may be inevitable that at certain times the virtual line connecting their representations in the virtual map may intersect representations of other objects. However, if that intersection persists for more than a certain period of time (e.g., 1 second), the navigation system 120 may respond by generating an output configured to cause UAV 100 to maneuver to avoid the intersection.

In FIG. 7 , the dotted line of sight 710 may represent the virtual line of sight connecting the representations of UAV 100 and subject 102 within a virtual environment (i.e., the computer-generated 3D model) representing physical environment 720. As human subject 102 begins to move within the physical environment, the virtual line 710 connecting the virtual representations moves as well. If the human subject 102 moves behind object 730, the virtual line within the 3D map will then intersect the corner of a virtual representation of physical object 730 as indicated by dotted line 712. When this intersection occurs in the virtual environment, the subject-relative objective to maintain visual contact is no longer satisfied in the physical environment. Note that this may represent a state several seconds in the future based on a predicted motion of the UAV 100 and/or subject 102. A current or predicted intersection of the virtual line of sight with a virtual representation of a physical object will therefore cause the navigation system 120 to generate an output to configured to cause the UAV 100 to maneuver to avoid the intersection. For example, the motion of the virtual line can be tracked and it may be determined that in order to avoid the intersection, UAV 100 should maneuver along flight path 706 as opposed to flight path 704 to keep the view of subject 102 unobstructed.

In some situations, intersection points along a virtual line can be analyzed differently depending on their distance to the UAV 100. This may be based on an assumption that motion by a UAV 100 generally has a greater impact on resolving visual occlusions caused by objects that are closer to the UAV 100. This assumption may depend on the size and/or shape of the obstructing object; however, in general, relatively minor maneuvers by UAV 100 may be sufficient to maintain line of sight with a subject around an object that is close to UAV 100. Conversely, more drastic maneuvers by UAV 100 may be necessary to maintain line of sight around an object that is closer to subject 102. This makes sense when again considering the scenario described in FIG. 7 . Although described as a single object 730, the virtual representation of object 1030 can also be described as multiple surfaces that intersect the virtual line at multiple points. For example, obstructed line of sight line 712 intersects a first surface of object 730 that faces UAV 100 at a first point and a second surface of object 730 that faces a future position of subject 102 at a second point. A minor maneuver along flight path 706 may be sufficient such that sight line 712 no longer intersects the first surface (i.e., the surface closest to UAV 100) at the first point. However, a more extended maneuver along flight path 706 may be necessary before sight line 712 no longer intersects the second surface (i.e., the surface closest to subject 102) at the second point, thereby establishing line of sight with subject 102.

In some embodiments, a subject-relative objective such maintaining line of sight may be built into the navigation system 120 as a core objective (e.g., similar to avoiding collisions), for example, to comply with a flight regulation. For example, a UAV 100 may be subject to a regulation that requires a human operator to maintain visual line of sight with the UAV 100. A simple control restraint on separation distance (i.e., range) between a subject (i.e., the human operator) and the UAV 100 may suffice to an extent but will not ensure that visual line of sight is maintained. Instead, the above described technique for maintaining line of sight can be utilized.

Subject-relative objectives may also apply to multiple simultaneously tracked subjects. In some cases, this may be accomplished by inputting multiple objectives (relative to each tracked subject) into the navigation system and allowing the navigation system to generate a planned trajectory to satisfy as many of the input subject-relative objectives as possible along with any other objectives (e.g., avoid collisions). Alternatively, or in addition, a single objective relative to multiple tracked subjects may be input contemplated. For example, a subject-relative objective may be defined relative to an average position and/or orientation of multiple tracked subjects in a scene.

Image-Relative Objectives

In some embodiments, an objective may be expressed in terms relative to images captured by one or more image capture devices 114/115 onboard the UAV 100. For example, an image-relative objective may be defined to keep certain tracked objects within an FOV of an image capture device 114/115, keep certain tracked objects at a particular position in FOV of the image capture device 114/115, keep the horizon at a particular position/orientation relative to the image capture device 114/115 etc.

FIG. 8 depicts an example image 802 captured (e.g., by an image capture device 114/115) of an object (e.g., a human subject 102). As suggested in FIG. 8 , an image-relative objective may include a target, for example, to keep the depiction of the tracked human subject 102 at a particular coordinate in the image space of the captured image 802. In the example scenario depicted in FIG. 8 , a target normalized image space coordinate for the subject 102 may be defined as (0.5, 0.7) with corresponding dead zones of 0.2 in the y direction and 0.7 in the x direction.

In order to satisfy certain image-relative objectives, a computing system associated with UAV 100 may process images received from the image capture devices 114/115 onboard the UAV 100 to perform an image space analysis of certain objects (e.g., a tracked subject or the horizon) detected in the captured images.

Semantic-Based Objectives

In some embodiments, objectives may be based on semantic understanding of the physical environment. Examples of such objectives may include avoiding backlighting by the sun, maintaining scene saliency (e.g., focusing on “interesting” objects or image regions), avoiding dangerous or critical areas, tracking certain classes of objects (e.g., people vs. animals), tracking objects performing a certain activities (e.g., people running vs. standing still), landmark reasoning (e.g., avoiding obfuscation of a tracked object), overall scene understanding (e.g., capturing an image of one object approaching another object), and the like. It shall be appreciated that these are only a few example semantic-based objectives provided for illustrative purposes, and are not to be construed as limiting. The types of semantic-based objectives that may be implemented may only be limited by the extent to which a computing system associated with the UAV 100 is able to gain a semantic understanding of the physical environment and the multiple objects occupying the physical environment.

FIG. 9 shows an example scenario that illustrates a semantic-based objective including a target that avoids backlighting by the sun when capturing images of a tracked object. As shown in FIG. 9 , a UAV 100 is in autonomous flight over a physical environment 920 while tracking and capturing images of a particular object (in this case human subject 102). The human subject 102 is lit by a light source 950 (in this example the Sun) from one side. Here, UAV 100 is shown at a current location (as indicated by the solid line quadcopter) opposite the light source 950 relative to the human subject 102. At this current position, images captured of human subject 102 (for example within FOV 910) are likely to be devoid of much detail of human subject 102 due to the shadow cast by the light source 950. In the case of a powerful light source 950 such as the Sun, the captured images may be completely washed out due to over exposure, particularly if the image capture device associated with UAV 100 is oriented so as to be pointed substantially in the direction of the light source 950.

Subjectively, backlighting during image capture is generally understood to result in poor quality images. Accordingly, in some embodiments, a semantic-based objective may be configured to avoid backlighting. To satisfy such an objective, a navigation system 120 may generate an output (e.g., control commands or a planned trajectory) configured to cause the UAV 100 to autonomously position itself substantially between certain light sources (e.g., the Sun) and a tracked subject 102 when capturing images of the tracked subject 102. Consider again the scenario depicted in FIG. 9 . Since UAV 100 is located opposite a major light source 950 while capturing images of subject 102, in order to satisfy a specified objective, a navigation system 120 may generate control an output configured to cause UAV 100 to autonomously maneuver along flight path 904 until, at a future time, UAV 100 is located substantially between light source 950 and subject 102 (as indicated by the dotted line quadcopter). A method for generating such an output may include, in addition to estimating the motions of UAV 100 and subject 102, also estimating a position of a light source 950. This may be accomplished in a number of ways for example, by processing images captured by an image capture device 114/115 associated with UAV 100 and/or based on localization data of known light sources (e.g., the Sun). Given global positioning information for UAV 100 and the current date/time, a localization system can determine if UAV 100 is pointed towards the Sun while capturing images of a subject 102.

In some embodiments, a semantic-based objective may include a target to capture images of “interesting” objects in the physical environment. This may be generally referred to as scene or visual saliency. The attention of humans and certain other animals tends to be attracted to visually salient stimuli. Visually salient stimuli may be based, for example, on the closest object roughly centered in an FOV, an object in motion, an object performing a certain activity of interest, etc.

What is deemed “interesting” or visually salient may of course differ depending on the context in which the UAV 100 is operating. As an illustrative example, an objective may be configured to cause a UAV 100 track and capture images of a particular class of object (e.g., people) and/or of a particular type of activity. For example, FIG. 10 shows an example scenario involving a UAV 100 in autonomous flight through a physical environment 1020. In this example scenario, an objective may be configured to track and capture images of people that are skiing. Successfully satisfying such an objective may require detection of objects in the physical environment 1020 as well as a semantic understanding of the scene in order to distinguish a person 102 b that is standing still or performing some other activity (e.g., walking) from a person 102 a that is skiing.

In order to satisfy the objective, a navigation system may generate an output (e.g., control commands or a planned trajectory) configured to cause the UAV 100 to follow a person skiing 102 a (when detected) and focus image capture on that person 102 a. In some embodiments, the UAV 100 may simply follow the tracked object at a set distance. Alternatively, or in addition, the UAV 100 may execute maneuvers in order to add a dynamic quality to the captured images. For example, as shown in FIG. 10 , the UAV 100 may autonomously maneuver along a path 1002 to capture the skier 102 a at different angles as the skier 102 a continues down the slope. In some cases, such maneuvers may be based on pre-scripted flying patterns that are triggered when a particular object (e.g., a skier 102 a) is detected. Alternatively, or in addition, flight paths that provide “interesting” shots may be learned by the system over time by applying machine learning.

The scenario depicted in FIG. 10 is provide for illustrative purposes and is not to be construed as limiting. Another example semantic-based objective for visual salience may include a target tracking and capturing images of a key individual in a team sporting event. Consider for example, a football game involving two teams, each with multiple players. To capture images of the game, a semantic-based objective may be configured to cause a UAV 100 to track and capture images of an object of interest such as the football, a player in current possession of the football, a player with imminent possession of the football (e.g., a receiver about to catch the football), the end zone, a referee, the coach, etc. Over the course of the game, the object or set of objects of interest will likely change from one moment to the next. Again, the manner in which the UAV 100 responds to satisfy the objective may be based on pre-scripted patterns of motion and image capture or may be learned, for example, by analyzing professional television broadcasts of sporting events.

High-Level Behavioral Objectives

Certain objectives may be based around high-level behavior such as maintaining a certain dynamic smoothness in proposed trajectories, avoiding exceeding dynamic airframe constrains, avoiding obstacle collisions, prioritizing avoiding collisions with certain classes of objects (e.g., people), avoiding running out of storage space for image capture, avoiding running out of power, etc.

As an illustrative example, FIG. 11 depicts an example scenario involving a UAV 100 with a high-level behavioral objective to avoid collisions with other objects. In the scenario depicted in FIG. 11 , a UAV 100 is in flight through a physical environment 1120 while capturing images of a human subject 102. As shown in FIG. 11 , UAV 100 may be in autonomous flight along a current planned flight path 1104 to maneuver to avoid a collision with another object 1130 in the physical environment while keeping human subject 102 in view (as indicated by FOV lines 1110). The example illustrated in FIG. 11 is idealized and shows a relatively large stationary object 1130 (for example a building or other structure), but the same concept may apply to avoid smaller mobile objects such as a bird in flight. As shown in FIG. 11 , based on the estimated motions of UAV 100 and subject 102, a navigation system 120 may generate an output (e.g., control commands or a planned trajectory) to maneuver UAV 100 along flight path 1104 to avoid object 1130 while keeping human subject 102 in view (as indicated by FOV lines 1110). Notably, this scenario illustrates a combination of multiple objectives, specifically maintaining line of sight with a tracked subject (as previously discussed) while avoiding collision. As will be discussed further, the multiple objectives may be weighted differently such that a navigation system 120 favors satisfying one objective (e.g., avoiding collision) over another (e.g., maintaining line of sight with a tracked subject) if both cannot be satisfied concurrently.

Another example high-level behavioral objective may include autonomously landing the UAV 100 when a power source (e.g., batteries) powering a propulsion system (e.g., the rotors) is at or below a threshold level of power (e.g., charge). For example, in some embodiments, if the batteries on the UAV 100 get below a certain threshold level (e.g., 5% charge), the UAV 100 may automatically land on the ground regardless of any other active objectives so as to avoid a loss of control and possible crash.

Another example high-level objective may include smoothing proposed trajectories. In many situations, particularly when performing image capture, abrupt changes in the direction of flight of the UAV 100 may not be preferred. Accordingly, in some embodiments, a navigations system may incorporate a high-level objective to maintain a certain smoothness in any generated planned trajectory.

As suggested by the aforementioned examples, some of these high-level behavioral objectives may be based around ensuring safe autonomous operation of the UAV 100. In some cases, such objectives may be built into a motion planning process of a navigation system 120 so as to always be actively considered when generating a planned trajectory. In other words, regardless of any objectives received through calls to the API 300, the motion planning system 130 of the navigations system may always take into account certain built-in objectives such as obstacle avoidance, dynamic airframe constraints.

Objective-Based Motion Planning Using an API

In some embodiments, a navigation system 120 (e.g., specifically a motion planning component 130) is configured to incorporate multiple objectives at any given time to generate an output such as a planned trajectory that can be used to guide the autonomous behavior of the UAV 100. The motion planning component 130 can take into consideration the dynamic constraints of the aircraft when generating outputs such as proposed trajectories. For example, given a similar set of objectives, a planned trajectory for a quadcopter UAV such as UAV 100 may be different than a planned trajectory for a fixed-wing UAV such as the UAV 100 b due to the different flight capabilities of the two craft.

The trajectory generation process can include gradient-based optimization, gradient-free optimization, sampling, end-to-end learning, or any combination thereof. The output of this trajectory generation process can be a planned trajectory over some time horizon (e.g., 10 seconds) that is configured to be interpreted and utilized by a flight controller 160 to generate control commands that cause the UAV 100 to maneuver according to the planned trajectory. A motion planning system 130 may continually perform the trajectory generation process as new perception inputs (e.g., images or other sensor data) and objective inputs are received. Accordingly, the planned trajectory may be continually updated over some time horizon thereby enabling the UAV 100 to dynamically and autonomously respond to changing conditions.

FIG. 12 shows a block diagram that illustrates an example system for objective-based motion planning using an API. As shown in FIG. 12 , a motion planning system 130 (e.g., as discussed with respect to FIG. 2 ) may generate and continually update a planned trajectory 1220 based on trajectory generation process involving one or more objectives (e.g., as previously described) and or more perception inputs 1206. The perception inputs 1206 may include images received from one or more image capture devices 114/115, results of processing such images (e.g., disparity images or depth values), and or sensor data from one or more other sensors 112 onboard the UAV 100 or associated with other computing devices (e.g., mobile device 104) in communication with the UAV 100. The one or more objectives 1202 utilized in the motion planning process may include built-in objectives governing high-level behavior (e.g., avoiding collision with other objects) as well as objectives based on inputs 1208.

The objective inputs 1208 may be in the form of calls to an API 300 by one or more applications 1210 associated with the UAV 100. An “application” in this context may include any set of instructions for performing a process to control or otherwise alter the behavior of the UAV 100 through an API 300. A developer (e.g., a third-party developer) can configure an application 1210 to send a command to the UAV 100 while in flight over a network API to alter one or more of the objectives 1202 utilized by the motion planning system 130 to alter the behavior of the UAV 100. As previously noted, the UAV 100 may be configured to maintain safe flight regardless of commands sent by an application. In other words, an application 1210 may not have access via the API 300 to alter certain core built-in objectives 1204 such as obstacle avoidance. The API 300 can therefore be used to implement applications such as a customize vehicle control, for example, through the use of a user computing device such as a mobile device 104. Such applications 1210 may be stored in a memory associated with the UAV 100 and/or stored in a memory of another computing device (e.g., mobile device 104) that is in communication (e.g., wireless communication) with the UAV 100.

Each of the objectives 1202 may be encoded as equations for incorporation in one or more motion planning equations utilized by the motion planning system 130 when generating a planned trajectory to satisfy the one or more objectives. Parameterization for the one or more objectives 1202 may be exposed to external entities such as external applications 1210 via the public facing API 300. In other words, an application 1210 may set values for certain objectives to affect the autonomous flight of the UAV 100 through the use of calls 1208 to the API 300.

Each given objective of the set of one or more objectives 1202 utilize in the motion planning process may include one or more defined parameterizations that are exposed through the API. For example, FIG. 13 shows an example objective 1302 that includes a target 1304, a dead-zone 1306, a weighting factor 1308, and other parameters 1310.

The target 1304 defines the goal of the particular objective that the motion planning system 130 will attempt to satisfy when proposing a trajectory 1220. For example, the target 1304 of a given objective may be to maintain line of sight with one or more detected objects in the physical environment as described with respect to FIG. 7 . The target 1304 may similarly be associated with any of the other example objectives described with respect to FIGS. 4-11 .

The dead-zone defines a region around the target 1304 in which the motion planning system 130 may not take action to correct. This dead-zone 1306 may be thought of as a tolerance level for satisfying a given target 1304. For example, FIG. 8 shows an example dead-zone definition in the context of an image-relative objective. As shown in FIG. 8 , the target of the example image-relative objective may be to maintain image capture of a tracked object 102 such that the tracked object appears at a coordinate of (0.5, 0.7) in the image space of the captured image 802. To avoid continuous adjustments based on slight deviations from this target, a dead-zone is defined to allow for some tolerance. For example, as shown in FIG. 8 , a dead-zone of 0.2 is defined in the y-direction and a dead-zone of 0.7 is defined in the x-direction. In other words, as long as the tracked object 102 appears within an area of the image bounded by the target and respective dead-zones, the objective is considered satisfied.

The weighting factor 1306 (also referred to as an “aggressiveness” factor) defines a relative level of impact the particular objective 1302 will have on the overall trajectory generation process performed by the motion planning system 130. Recall that a particular objective 1302 may be one of several objectives 1202 that may include competing targets. In an ideal scenario, the motion planning system 130 will generate a planned trajectory 1220 that perfectly satisfies all of the relevant objectives at any given moment. For example, the motion planning system 130 may generate a planned trajectory that maneuvers the UAV 100 to a particular GPS coordinate while following a tracked object, capturing images of the tracked object, maintaining line of sight with the tracked object, and avoiding collisions with other objects. In practice, such an ideal scenario may be rare. Accordingly, the motion planning system 130 may need to favor one objective over another when the satisfaction of both is impossible or impractical (for any number of reasons). The weighting factors for each of the objectives 1202 define how they will be considered by the motion planning system 130.

In an example embodiment, a weighting factor is numerical value on a scale of 0.0 to 1.0. A value of 0.0 for a particular objective may indicate that the motion planning system 130 can completely ignore the objective (if necessary), while a value of 1.0 may indicate that the motion planning system 130 will make a maximum effort to satisfy the objective while maintaining safe flight. A value of 0.0 may similarly be associated with an inactive objective and may be set to zero, for example, in response to toggling by an application 1210 of the objective from an active state to an inactive state. Low weighting factor values (e.g., 0.0-0.4) may be set for certain objectives that are based around subjective or aesthetic targets such as maintaining visual saliency in the captured images. Conversely, higher weighting factor values (e.g., 0.5-1.0) may be set for more critical objectives such as avoiding a collision with another object.

In some embodiments, the weighting factor values 1308 may remain static as a planned trajectory is continually updated while the UAV 100 is in flight. Alternatively, or in addition, weighting factors for certain objectives may dynamically change based on changing conditions, while the UAV 100 is in flight. For example, an objective to avoid an area associated with depth value calculations in captured images (e.g., due to low light conditions) may have a variable weighting factor that increases or decreases based on other perceived threats to the safe operation of the UAV 100. In some embodiments, an objective may be associated with multiple weighting factor values that change depending on how the objective is to be applied. For example, a collision avoidance objective may utilize a different weighting factor depending on the class of a detected object that is to be avoided. As an illustrative example, the system may be configured to more heavily favor avoiding a collision with a person or animal as opposed to avoiding a collision with a building or tree.

In some embodiments, a notification is returned to an API caller (e.g., an application 1210) in the event that an objective is requested (e.g., via a call 1208 to an API 300), but not satisfied (e.g., due to competing objectives, vehicle constraints, or other reasons). The API 300 may provide an endpoint for providing this notification so that the caller (e.g., an application 1210) can take appropriate action such as notifying a user, adjusting the requested objective, etc.

Applications and Skills

As previously discussed, applications (e.g., applications 1210) can be built using a development platform and the associated development tools offered by the platform (e.g., a public facing API 300) to augment the behavior of a UAV 100 and/or an experience of a user interacting with the UAV 100. In some embodiments, particularly in the context of a UAV 100 with image capture capabilities, applications can be developed around sets of instructions and assets that enable high-level autonomous behavior by the UAV 100. These instructions and/or assets may govern various aspects of the behavior of the UAV 100, the capture and processing of images by the UAV 100, and user interactions with the UAV 100. Certain sets of instructions and/or assets are referred to herein as “skills.”

As shown in FIG. 14 , an application 1410 may include one or more skills 1 through M. Further, each skill may include instructions related to certain navigation or image capture objectives 1420-1 through M, imaging effects 1422-1, visualizations 1424-1 through M, and other features 1426-1 through M.

For example, with respect to skill 1, objective(s) 1420-1 may include instructions for modifying the objectives utilized by a motion planning system 130 of the UAV 100, for example, by generating calls to an API 300 to set and/or modify certain parameters of one or more objectives. These instructions may govern the motion of the UAV 100 as well as other behavioral aspects such as object tracking, adjusting the orientation of an image capture device 115, etc.

Imaging effects 1422-1 may include instructions and/or assets for processing images captured by an image capture device 114/115 to change the appearance of captured images. Imaging effects may include any manipulations made to the captured images such scaling, geometric transformations (2D and/or 3D), transparency operations, splicing and/or cropping, sharpening, color correction, contrast adjustment, filters, etc. For example, a developer may configure a skill to present options to a user to select various pre-defined imaging effects to apply in real time as the UAV is in flight and capturing images and/or as part of a post-production process. Alternatively, or in addition, a developer may configure a skill to automatically apply certain imaging effects (in real time or post-production) based on contextual cues in the captured images. For example, a skill may be configured to apply a particular imaging effect (e.g., a predefined filter) to captured images in response to detecting a tracking a particular class of object or activity in the captured images.

Visualizations 1422-1 may include instructions and/or assets for providing visual output to a user. For example, visualizations 1422-1 may include augmented reality (AR) object descriptions that can be rendered in real-time or near-real-time (e.g., within milliseconds) to generate AR overlays that are displayed relative to tracked objects or other elements in the physical environment. An example of an augmented reality interface that may be implemented in conjunction with a UAV 100 is described with respect to FIG. 26 .

In some embodiments, the UAV 100 may include onboard memory for storing one or more skills as well as a sandboxed execution environment executing the skills to modify the behavior of UAV 100. For example, the sandboxed execution environment may be configured such that executing skills impact the behavior of the UAV 100 through calls to the API 300, but otherwise do not impact operation of the core navigations system 120. In this way, active skills can be safely changed on the fly while the UAV 100 is in flight without negatively impacting the safe flight of the UAV 100. In some embodiments, skills may execute at an external device such as a mobile device 104 and/or at an external data processing service such as a cloud-based computing environment utilizing multiple machines. In such cases, execution of the skills may generate outputs (e.g., control commands) that are then transmitted to the UAV 100 (e.g., via a wireless communication link) to control certain behavior of the UAV 100.

Skills can be configured to handle certain inputs from external sources to govern any of the aforementioned behaviors of a UAV 100. For example, a skill can be configured to receive inputs from a mobile device 104 (e.g., based on inputs by a user), from another UAV, from a cloud-computing services, or from any other external sources. Such inputs may cause the skill to govern behavior by the UAV 100 such as maneuvers or additional objectives that reside in a null-space of a set of objectives specified by the skill and/or alterations of a set of active objectives associated with a skill, in their set-point, dead-zone, or weighting factor settings.

In some embodiments, skills can be configured to include adjustable settings that can be set (e.g., based on input from a user via an application) while the UAV 100 is in flight. For example, a skill based around tracking and capturing images of objects in the physical environment can be configured to respond to a user input identifying a particular object to track. Such a user input may be received via an interface similar to the AR interface described with respect to FIG. 26 .

The example application 1410 depicted in FIG. 14 may represent a third-party application developed by the same developer that has developed skills 1-M. In such an embodiment, the UAV 100 and any associated mobile device 104 may be configured to store and execute one or more different first-party and/or third-party applications, each of the applications including one or more skills that affect the behavior of the UAV 100. To change the autonomous behavior of the UAV 100, a user may select between the various applications.

Alternatively, in some embodiments, application 1410 may represent a single application configured to implement the functionalities of one or more skills developed by different developers. For example, application 1410 may represent a first-party application developed by (or controlled by) a provider of UAV 100. In such an embodiment, the application 1410 may be configured to implement one or more different skills from different sources. The skills may be conceptualized as plugins or extensions to the application. As will be described in more detail, a user of the application (i.e., an end user of the UAV) may utilize an online “app store” to select or download skills or sets of skills (“skillsets”) that have been developed by various third-party developers to extend or otherwise modify the functionality of the UAV 100.

Implementation of Applications and Skills at a UAV

FIG. 15 shows a diagram illustrating an example implementation of an application 1510 including multiple skills 1530 in a system involving a UAV 100 and an associated mobile device 104 (e.g., similar to the system depicted in FIG. 1A). As shown in FIG. 15 , and as explained previously, the UAV 100 includes a navigation system 120. Perception, navigation, and flight control software may be encapsulated into navigation system 120 which can be conceptualized as a black box “autonomy engine.” This navigation system 120 exposes a set of objectives to control the behavior of the UAV 100 during flight, for example, via an API 1500. The API 1500 may be the same or similar to API 300 described earlier.

The API 1500 can be conceptualized as a layer above the navigation system 120 that exposes these objectives to one or more active skills 1532. More specifically, the API 1500 exposes the objectives as a set of “knobs” to the active skill 1532. To impact automated behavior, the active skill “turns” the exposed knobs, for example, by adjusting certain parameters (e.g., target, weight, etc.) associated with the objectives. Adjustments, by the active skill 1532, of the objective knobs are input, via the API 1500, as objective inputs to the navigation system 120 to control automated behavior.

As implied above, a given application 1510 may include multiple skills 1530 including, for example, skills developed by a provider of the UAV 100 and/or skills developed by a third-party developer. Interaction between a user and the UAV 100 according to the one or more skills 1530 may be via an application graphical user interface (GUI) 1536 displayed via a mobile device 104 such as a smart phone. At any given moment, one or more of the skills 1530 may be selected, for example, via user interaction with the application GUI 1536 to govern autonomous behavior by the UAV 100. These selected one or more skills are the active skills 1532 which impact the autonomous behavior of the UAV 100 by turning the objective knobs exposed by the API 1500. Accordingly, the application 1510 may also include one or more inactive skills 1534 at any given time that are not actively impacting the autonomous behavior of the UAV 100.

In some embodiments, the application GUI 1536 changes based on the currently active one or more skills 1532. For example, a user may select, via the application GUI 1536, an “orbit subject” skill. In response to the selection, the “orbit subject” skill is set as the active skill impacting the autonomous behavior of the UAV 100. Further, the “orbit subject” skill may be associated with specific interactive graphical interface elements that are exposed to the user via the application GUI 1536. Graphical interface elements specific to an “orbit subject” skill may include, for example, an interactive element to select a subject, an interactive element to set a rate of orbit about the selected subject, etc. These interactive graphical interface elements are specific to the selected skill. The interactive graphical interface elements will change in response to a user selecting a different skill from the one or more skills 1530. The graphical interface elements can also be changed by a skill, while active, for example, in response to environmental factors or in response to detected events. For example, a new interactive graphical interface element (e.g., a button) may be displayed by an active skill in response to detecting an obstacle, human subjects, or other objects in the physical environment.

The application 1510 is displayed in FIG. 15 as spanning across both the UAV 100 and the mobile device 104, with the skills 1534 located at the UAV 100 and the GUI 1536. This is just an example provided for illustrative purposes; the actual components of any given application 1510 may be organized differently in other embodiments and may be instantiated at more or fewer computing devices than is depicted in FIG. 15 . For example, in some embodiments, the skills 1530 may be included in instructions in memory at the mobile device 104. In such an embodiment, the mobile device may be configured to wirelessly transmit calls to the API 1500 based on outputs by the skills 1530 at the mobile device 104.

FIG. 16 shows a flow diagram of an example process 1600 for autonomously controlling an autonomous vehicle using one or more skills. Example process 1600 can be executed by any type of computer system associated with an autonomous vehicle. For example, process 1600 may be executed by a computer system associated with navigation system 120 of UAV 100. In some embodiments, the example process 1600 depicted in FIG. 16 may be represented in instructions stored in memory that are then executed by a processor. The process 1600 described with respect to FIG. 16 is an example provided for illustrative purposes and is not to be construed as limiting. Other processes may include more or fewer steps than depicted, while remaining within the scope of the present disclosure. Further, the steps depicted in example process 1600 may be performed in a different order than is shown.

Example process 1600 begins at step 1602 with exposing one or more variable parameters associated with a behavioral objective via an API (e.g., API 1500). As previously discussed, the behavioral objective may be one of multiple behavioral objectives that are applied by a motion planner 130 associated with navigation system 120 as part of a multi-objective trajectory generation process. As depicted in FIG. 15 , the variable parameters can be exposed to one or more skills 1530 including skills developed by a third-party developer.

Example process 1600 continues at step 1604 with receiving, via the API, an input indicative of a request to adjust a particular variable parameter of the behavioral objective. As previously discussed, in some embodiments, this request may be in the form of a call to the API. In some embodiments, the request is received from an application executing at the autonomous vehicle (e.g., application1 1510). In some embodiments, the request is from a particular software module of the application (e.g., active skill 1532). In some embodiments, the software module (i.e., skill) submitting the request may have been developed by a third-party developer that did not develop the application. In other words, the request may be from a custom extension or plugin of the application that was developed by a separate third-party developer.

Example process 1600 continues at step 1606 with adjusting the variable parameter of the behavioral objective based on the request received at step 1604.

Example process 1600 continues at step 1608 with receiving perception inputs from one or more sensors associated with the autonomous vehicle. The perception inputs may include images received from one or more image capture devices 114/115, results of processing such images (e.g., disparity images or depth values), and or sensor data from one or more other sensors 112 onboard the UAV 100 or associated with other computing devices (e.g., mobile device 104) in communication with the UAV 100.

Example process 1600 continues at step 1610 with the processing perception inputs and the behavioral objective to generate a planned trajectory through a physical environment, for example, as discussed with respect to FIG. 12 . In some embodiments, the planned trajectory is continually updated as the parameters of the one or more behavioral objectives are adjusted and/or as new perception inputs are received.

Example process 1600 concludes at step 1612 with causing the autonomous vehicle to autonomously maneuver along the planned trajectory generated at step 1610.

FIG. 17 shows a flow diagram of an example process 1700 for controlling an autonomous vehicle using one or more skills. Example process 1600 can be executed by any type of computer system associated with an autonomous vehicle. For example, process 1700 may be executed by a computer system associated with a mobile device 104 that is communicatively coupled to the autonomous vehicle. In some embodiments, the example process 1700 depicted in FIG. 17 may be represented in instructions stored in memory that are then executed by a processor. The process 1700 described with respect to FIG. 17 is an example provided for illustrative purposes and is not to be construed as limiting. Other processes may include more or fewer steps than depicted, while remaining within the scope of the present disclosure. Further, the steps depicted in example process 1700 may be performed in a different order than is shown.

Example process 1700 begins at step 1702 with displaying a GUI at a user computing device. For example, as depicted in FIG. 15 , an application GUI 1536 associated with application 1510 may be displayed at a mobile device 104 that is communicatively coupled (e.g., via wireless communications interface 116) to an autonomous vehicle such as UAV 100.

In some embodiments, the GUI displayed at step 1702 may include live video stream from a camera coupled to the autonomous vehicle. For example, application GUI 1536 may display images (including a live video stream) that are captured by an image capture device 115 at UAV 100 and received over a wireless communication link 116.

Example process 1700 continues at step 1704 with displaying, in the GUI, an interactive menu for selecting from multiple different available skills. For example, the application GUI 1536 associated with application 1510 may display an interactive menu that enables a user of mobile device 104 to select from the multiple available skills 1530. In some embodiments, each of the selectable skills depicted in the menu are associated with a different mode of operation of an autonomous vehicle. For example, menu 2720 depicted in FIG. 27 includes multiple different modes of operations such as “boomerang,” “cablecam,” “follow,” “dronie,” “rocket,” and “spiral.” One or more of these modes of operation depicted in menu 2720 may be associated with a skill developed by a third-party developer.

Example process 1700 continues at step 1706 with receiving, via the interactive menu, a selection of a particular skill from the multiple available skills. For example, a user of mobile device 104 may input the selection using an input device associated with mobile device 104 such as a touch screen display.

Example process 1700 continues at step 1708 with activating the particular skill based on the selection received at step 1706. For example, as depicted in FIG. 15 , an active skill 1532 may represent a skill that has been selected by a user via application GUI 1536, while inactive skills 1534 represent the other available skills that have not been selected.

Example process 1700 continues at step 1710 with updating the display of the GUI to include a particular interactive element associated with the particular skill in response to the activation. For example, as discussed with respect to FIG. 15 , the application GUI 1536 will change to include certain interactive elements that are specified by the active skill 1532.

Although not depicted in the flow diagram of FIG. 17 , in some embodiments, example process 1700 may further include generating an augmented reality element based on the selected particular skill and updating the GUI to display the augmented reality element. In embodiments where the GUI displays a live video stream from an image capture device coupled to the vehicle, the augmented reality element may be displayed over a portion of the live video stream.

Example process 1700 continues at step 1712 with detecting a user interaction with the particular interactive element in the GUI.

Example process 1700 concludes at step 1714 with transmitting a command signal to the autonomous vehicle based on the detected interaction. For example, as described with respect to FIG. 15 , in response to user interaction with application GUI 1536, a command signal can be transmitted from mobile device 104 to UAV 100, for example, over a wireless communication link 116. The command signal may be configured to cause a call to the API 1500 associated with navigation system 120. Specifically, the command signal may be configured to cause the corresponding active skill 1532 to generate the call to the API 1500 to adjust a parameter of a behavioral objective associated with a multi-objective trajectory generation process executed by the navigation system 120.

Example Application and Skills Platform

FIG. 18 shows a diagram illustrating an example implementation of a platform 1820 for developing and/or distributing applications and skills. As shown in FIG. 18 , the example platform 1820 includes a developer console 1840 that includes or is configured to enable access to a mobile SDK 1842, a skills SDK 1844, and one or more simulation environments 1866. A developer may access the developer console 1840 of platform 1820 to develop applications and skills, for example, by utilizing a developer application or web browser 1808 at a developer device 1806. The developer device 1806 may include any type of computing device such as personal computer, mobile device (e.g., mobile device 104), etc. The platform 1820 may host one or more available skillsets 1830 that can be implemented at any number of UAVs. The available skillsets 1830 may include first-party skillsets 1832 developed by a provider of platform 1820 as well as third-party skillsets 1834 developed by third-party software developers, for example, through the use of the developer console 1840. As will be described, UAV users may access new/updated applications and skillsets for use with their respective UAVs through an online store 1850 provided by platform 1820. Selected applications and/or skills may be “delivered” to UAVs and/or mobile devices using configuration system 1860 and associated configuration database 1862.

The platform 1820 may represent any combination of hardware and or/software for executing instructions to carry out the functionalities described herein. For example, the platform 1820 may be implemented using one or more network-connected server computer systems (physical and/or virtual) with associated non-transitory processor-readable storage media or other data storage facilities. For example, one or more databases for storing data (including metadata) maybe accessible to the server computer systems. Instructions for carrying out certain processes described herein may be implemented as software instantiated in a computer-readable medium or computer-readable storage medium on a machine, in firmware, in hardware, in a combination thereof, or in any applicable known or convenient device or system. This and other modules, sub-modules, or engines described in this specification are intended to include any machine, manufacture, or composition of matter capable of carrying out at least some of the functionality described implicitly, explicitly, or inherently in this specification, and/or carrying out equivalent functionality.

In some embodiments, the platform 1820 comprises an internet-based web service and/or a cloud-computing service. For example, the platform 1820 may be implemented (at least partially) in instructions executed by computing entities in a cloud-computing environment. Such a cloud-computing environment may be hosted by a third-party cloud-computing provider. For example, Amazon™ offers cloud computing services as part of the Amazon™ Web Services (AWS) platform. One or more of the functionalities of the platform 1820 may be implemented using products and services associated with a cloud-computing platform such as AWS. In an illustrative embodiment, computing functionality is provided using virtual computing entities (e.g., Amazon™ EC2 virtual server instances and or Lambda event-based computing instances) executing across one or more physical computing devices and storage functionality is provided using scalable cloud-based storage (e.g., Amazon™ S3 storage) and/or managed databases, data warehouses, etc. (e.g., Amazon™ Aurora, Amazon™ DynamoDB, Amazon™ Redshift, Google™ Spanner, etc.).

Various users may use computing devices to interact with and access the services of the platform 1820. Users, in this context, may include users of UAVs as well as developers of applications and/or skills to be implemented at UAVs. In some embodiments, computing devices may execute an application or “app” that communicates with the platform 1820 via any suitable communications interface. In some embodiments, interaction between an application instantiated at a computing device and the platform 1820 may be via one or more cloud APIs. Computing devices may include any number of types of devices configured to process data and communicate with other devices via a computing network. As previously discussed, computing devices may include UAVs 100, mobile devices 104, developer devices 1806, and any other computing devices.

The various systems, subsystems, and/or processor-based devices described with respect to the system depicted in FIG. 18 may be capable of communications via the one or more computer networks which may be, for instance, packet switched communications networks, such as the Internet, Worldwide Web portion of the Internet, extranets, intranets, and/or various other types of telecommunications networks such as cellular phone and data networks or channels, plain old telephone system (POTS) networks, etc. The type of communications infrastructure should not be considered limiting.

The mobile SDK 1842 includes tools and/or resources to enable a third-party developer to develop third-party mobile applications or “apps” that can be implemented at a UAV 100 and/or mobile device 104 to govern autonomous behavior by the UAV 100. For example, application 1510 may be a third-party app developed using the mobile SDK 1842.

In some embodiments, a developer can bundle skills (pre-built or developer-created) in a third-party mobile application created using the mobile SDK 1842. Skills bundled in a third-party application may include pre-built or packaged first-party skillsets 1832, pre-built or packaged skillsets by other developers (e.g., third-party skillsets 1834), and or customized skillsets developed using the skills SDK 1844. For example, using application 1608, a developer can select and download skills and skillsets from the available skillsets 1830, edit downloaded skills or skillsets, and/or write customized skillsets, for example, using libraries (e.g., python libraries) provided via the skills SDK 1844. This enables a developer to ship several skills or skillsets to users via custom applications.

In some embodiments, applications developed using the mobile SDK 1842 are configured to transmit remote procedure call (RPC) communications to an active skill 1532 running at a given UAV 100 to govern autonomous behavior by the UAV 100. For example, in response to user input via an application GUI 1536, an application 1510 may communicate with an active skill 1532 to adjust one or more objective knobs exposed by API 1500 (shown in FIG. 15 ).

In some embodiments, applications (e.g., application 1510) are configured to pull configuration information from cloud API servers of platform 1820. This configuration information may include, for example, settings, skillsets, available simulators, and other configurations that are specifically tailored to a given user of the application. In an illustrative example, a user of UAV 100 and mobile device 104 has an account with platform 1820. Information associated with the user is stored in a configuration database 1862. As mentioned, the configuration information associated with the user that is stored in the configuration database 1862 may include user settings as well as identification of one or more skills (or skillsets) that the user has either selected or purchased (e.g., via an app store 1850). In some embodiments, when the user is logged in via application 1510, the application can automatically receive (e.g., pull) configuration information from platform 1820, for example, via configuration system 1860. In other words, skills can be shipped automatically ‘under the hood’ from a cloud API of platform 1820 to an application 1510 (first-party or third-party application) instantly via a configuration system 1860, for example, by transmitting configuration information (configurations and code) tailored to a specific user of application 1510. This enables the skills 1530 associated with a given application 1510 to update transparently without input by the user and without requiring recompiling and/or redownloading of the application 1510.

Simulation Environments for Developing Applications and Skills

As discussed, the platform 1820 may enable developers to create their own applications and/or skills, for example, through the use of an application 1808 at a developer device 1806 (which may be mobile device 104). Without requiring a deep understanding of the complex processes involved in the autonomous behavior of the UAV 100, developers can create customized applications and/or skills that combine various behavior objectives with imaging effects, visualizations, etc., as previously discussed. These components may be presented via the application 1808 as tools that can be selected and configured to create customized applications and/or skills.

One or more simulation environments may be implemented to aid developers in the development and testing of applications and/or skills. For example, in some embodiments, the developer console 1840 enables a developer to utilize one or more simulation environments 1866 (e.g., cloud-based simulation environments) to test the functionality of mobile applications and/or skills that the developer has created. The developer can synchronize local skillsets at the developer application 1808 to the developer console 1840 to “stage” the files for testing before publishing to other users. Through the developer console 1840 and/or developer application 1808, the developer may access a list of available simulators (i.e., simulated UAVs) that may be assigned based on user account to utilize in one or more simulation environments 1866. A developer can “fly” applications and/or skills they have created in the one or more available simulators to test their functionality in real-world conditions.

The one or more simulation environments 1866 may model the physical properties of the real world within which one or more simulated vehicles can operate. For example, a simulated environment 1866 may include a videogame-like 3D model of a physical environment as well as physics engine configured to simulate the motion of simulated 3D objects within the 3D model of the physical environment. The physics engine may simulate various properties of real-world physical systems such as rigid body dynamics (including collision detection), soft body dynamics, fluid dynamics, etc. Simulated vehicles (e.g., simulated UAV) may comprise virtualized representations of the onboard hardware and software of real vehicles. In other words, a simulated UAV may include all of the actual software onboard a real UAV 100 (e.g., software associated with navigation system 120) as well as virtualize representations of onboard hardware used to implement the software (e.g., virtual processors, virtual sensors, etc.). Each simulated vehicle may include a dynamic model that approximate the physical properties of corresponding physical vehicles and is configured to interact with the simulated environment 1866 to approximate the motion of corresponding physical vehicles in a physical environment. For example, a simulated UAV may include a dynamic model that approximates the aerodynamic properties of the body of a physical UAV 100 as well as the properties of the propulsion systems onboard a physical UAV 100.

A developer can test the response of a physical UAV 100 by installing applications and/or skills into one or more simulated vehicles, “flying” simulated vehicles in the simulated environment 1866, and observing the automated behavior of the simulated vehicles within the simulated environment 1666, when executing installed applications and/or skills. For example, a developer may wish to test a response by a UAV 100 to a customized skill based around tracking and capturing images of objects in motion by first simulating the response. The simulation environment 1866 may simulate such objects in motion that are then detected by virtualized perception systems (e.g., virtual image capture devices, etc.) onboard a simulated UAV. Applications and/or skills installed in the simulated UAV may then guide the autonomous behavior of the simulated UAV within the simulated environment based on the data gathered by the virtualized perception systems.

Further, a developer may connect a mobile device (physical and/or simulated) to a given simulation environment 1866 running a simulated UAV to test the real-world interaction between a UAV 100 and mobile device 104 implementing an application and/or skill. For example, a developer may connect a mobile application 1510 at a physical mobile device 104 to a simulated UAV operating within a simulated environment 1866 as if the mobile application 1510 was connecting to a real UAV 100. Real vehicles and simulated vehicles expose the same set of API, so an application connecting to such vehicles does not need to know the difference between the simulated vehicle and the real vehicle. In some embodiments, the mobile device 104 is configured to display a visual output, for example, in the form of a live video feed from image capture devices onboard a physical UAV 100. If the mobile device 104 is instead used to connect with a simulated UAV operating in a simulated environment 1866, this visual feed may instead comprise a rendering of the 3D model of the physical environment included in the simulated environment 1866.

In some embodiments, platform 1820 may enable users (e.g., developers) to run simulated environments that are limited for their individual use or use by other invited users. Alternatively, or in addition, multiple users may connect to the same simulation hosted by the platform 1820 to interact with each other through simulated vehicles. For example, platform 1820 may enable a cluster of simulated vehicles to be run in a simulated environment and allow users to connect to the simulated vehicles.

The platform 1820 may enable developers to invite other users to join and participate in certain simulations. For example, a developer may invite users into a simulation environment to try out new applications and/or skills they are working on. Users may connect to a particular simulated vehicle maintained by the developer and operate the simulated vehicle using developer applications and/or skills, via their mobile device as they would a real vehicle. In some embodiments, a developer may invite other users to participate, for example, by controlling subjects within the 3D world of the simulation environment to test the response of the simulated vehicle to simulated subjects controlled by actual people instead of bots.

FIG. 19 shows a flow diagram of an example process 1900 for generating skills and/or applications using platform 1820. Example process 1900 can be executed by any type of computer system. For example, process 1900 may be executed by a computer system associated with developer device 1806 and/or platform 1820. In some embodiments, the example process 1900 depicted in FIG. 19 may be represented in instructions stored in memory that are then executed by a processor. The process 1900 described with respect to FIG. 19 is an example provided for illustrative purposes and is not to be construed as limiting. Other processes may include more or fewer steps than depicted, while remaining within the scope of the present disclosure. Further, the steps depicted in example process 1900 may be performed in a different order than is shown.

Example process 1900 begins at step 1902 with enabling access to a developer console for developing software modules (i.e., skills and/or applications) for use with an autonomous vehicle. For example, step 1902 may include enabling access to developer console 1840 and the associated tools such as mobile SDK 1842, skills SDK 1844, and or a simulation environment 1866.

Example process 1900 continues at step 1904 with receiving, via the developer console, a user input specifying instructions for causing an execution computer system at an autonomous vehicle to perform one or more operations. For example, the user input may be received from a developer user (e.g., a third-party developer user) that specifies instructions that will be included in a skill and/or application. The specified instructions may be in the form of computer code and/or selections from an interface associated with the developer console. For example, in some embodiments a developer user may write all of the computer code that will be included as part of a software module (i.e., a skill and/or application). In some embodiments, the developer user may utilize one or more tools associated with an SDK (e.g., mobile SDK 1842 and/or skills SDK 1844) to assist in specifying the instructions. In some embodiments, some or all of the specified instructions may include one or more predefined code libraries that are part of an SDK.

In some embodiments, example process 1900 may additionally include presenting, via the developer console 1840, an option to select from multiple predefined code libraries, for example, associated with an SDK. In some cases, these predefined code libraries may be configured for use with an API associated with an autonomous navigation system of an autonomous vehicle (e.g., API 1500 of navigation system 120). A user input can then be received, via the developer console 1840, that selects a particular code library from the multiple predefined code libraries. In such an embodiments, the specified instructions may be based, at least in part, on the selected predefined code library.

In some embodiments, example process 1900 may additionally include presenting, via a developer console 1840, an option to select from multiple predefined interactive GUI elements that can be used to control the operations performed at the execution computer system of the autonomous vehicle. The various predefined interactive elements may include, for example, predefined buttons, slider bars, etc. The predefined interactive elements may be configured to operate seamlessly with an existing GUI (e.g., application GUI 1536) that is used to receive user commands that guide the behavior of an autonomous vehicle. In other words, a developer user can define how the interactive elements specific to their skill will appear and operate by selecting from the one or more predefined interactive elements. In such an embodiments, the specified instructions may be based, at least in part, on the selected predefined code library.

In some embodiments, example process 1900 may additionally include presenting, via a developer console 1840, an option to add one or more digital assets (e.g., images, video, 3D models, etc.) and receiving, via the developer console, a user input including or otherwise specifying a digital asset to be added. In some embodiments, the input may include an uploaded copy of the digital asset. In some embodiments, the input may include a link to download the digital asset. As previously discussed, digital assets can be used, for example, to customize interactive elements of the application GUI 1536, present visual augmentations via the application GUI 1536, etc.

In some embodiments the digital asset is included in the software module that is generated as part of process 1900. In such embodiments, the instructions included in the software module may cause an execution computer system (at the autonomous vehicle or a corresponding mobile device 104) to process the included digital asset to, for example, generate an interactive element that is displayed in the application GUI 1536 and/or generate a visual augmentation (e.g., a rendering of a 3D model) that is displayed in the application GUI 1536.

The specified instructions may be customized by the developer user to cause an execution computer system at an autonomous vehicle to perform various types of operations, but generally the operations may include transmitting, or otherwise communicating, a call to an API associated with an autonomous navigation system of autonomous vehicle (e.g., API 1500 of navigation system 120). As previously discussed, the call to the API will be configured to adjust a parameter of a behavioral objective associated with a trajectory generation process performed by the autonomous navigation system.

Example process 1900 continues at step 1906 with generating a software module that includes the specified instructions and that is executable at the execution computer system at the autonomous vehicle to guide autonomous behavior by the autonomous vehicle. In other words, step 1906 includes generating a skill and/or an application based on the instructions specified by a developer user via the developer console 1840. In the case of a skill, the generated software module may extend the functionality of an existing application at the autonomous vehicle.

Example process 1900 continues at step 1908 with enabling access to the generated software module. For example, custom skills and/or applications created by developer users may be hosted at platform 1820 (e.g., via an online store 1850) where they can be accessed by multiple end users for use in their respective autonomous vehicles.

In some embodiments, before enabling access to the generate software module, example process 1900 may include testing the generated software module in a simulation environment such as simulation environment 1866. In other words, example process 1900 may further include enabling access, via the developer console 1840, to a simulation environment 1866 to test the functionality of the generated software module prior to deploying the generated software module to the execution computer system at the autonomous vehicle.

Global Simulation Environment

In some embodiments, platform 1820 may host a global simulation environment that provides an overall world-scale, real-time, simulation of the overall physical planet. FIG. 20 shows a diagram illustrating an example implementation of a global simulation environment 2067 at platform 1820. The global simulation environment 2067 may be continuously updated with real-world data from various sources such as physical UAVs 100 a, 100 d in flight in the physical environment, mobile devices 104 a, 104 b in the physical environment, as well as other data sources 2050 such as other sensor devices, mapping/location databases (e.g., Google Maps, GIS, etc.). Maps and sensor data from the various data sources can be fused into a global, continually updated 3D map of the physical planet. The continually updated global simulation environment 2067 may also include simulated objects corresponding to real-world physical objects. For example, a human subject tracked by a physical UAV 100 a in the real world can be represented as a dynamic virtual object occupying the global simulated environment 2067. The location and motion of the dynamic virtual object is continually updated within the global simulation environment 2067 based on a flow of sensor data received from the physical UAV 100 a.

Simulated vehicles and other object can be placed within the global simulation environment 2067. In some cases, simulated vehicles and/or objects may correspond with real-world physical vehicles and other objects. For example, UAV simulations 2010 a and 2010 d corresponding to real-world physical UAVs 100 a and 100 d (respectively) may occupy the global simulation environment at locations corresponding to the locations of their real-world counterparts. As the physical UAV 100 a flies through the real-world physical environment, a UAV simulation 2010 a flies through the global simulation environment 2067. Real world vehicles and devices (e.g., UAVs 100 a/100 d and user devices 104 a/104 b) can post their current (and planned) trajectory information to the platform 1820 where it is incorporated into the global simulation environment 2067 for improved motion predictions, visualizations, etc.

The real-time nature of the global simulation environment 2067 enables developers to test their applications and/or skills in as real a setting as possible short of actually testing in a real-world physical vehicle. For example, as shown in FIG. 20 , different developers 1806 b and 1806 c can test their applications and/or skills on UAV simulations 2010 b and 2010 c (respectively) that occupy the global simulation environment 2067. Each developer may run multiple simulated vehicles.

The global simulation environment 2067 may also enable users (e.g., organizations) to perform activities other than software development such as monitoring real-world activity, inspecting sites in real-time, playing back logged data to see past real-world activity, etc.

Advanced vehicle-control interfaces can also be built on top of or otherwise utilize the continually updated global simulation environment 2067. For example, autonomous vehicles can be routed automatically to certain locations in the physical environment that have not been scanned to improve detail within the global simulation environment 2067. As another example, real-world vehicles such as UAVs 100 a/100 b may generated better autonomous flight paths by leveraging the global map and location/motion information provided by other vehicles and devices.

Custom Machine Learning Models

The navigation system 120 of an autonomous UAV 100 may rely on one or more machine learning models. As an illustrative example, the navigation system 120 may process captured digital images using neural networks to detect objects in captured images and distinguish between instances of captured objects. This complex processing is typically performed within the sandboxed environment of the navigation system and is not exposed to applications and/or skills developed by third-party developers. However, to extend the capabilities of developer-created applications and skills, the platform 1820 may enable developers to upload customized machine learning models and/or training data specifically tailored to certain tasks for integration into the UAV 100.

Image-based training data can be utilized to develop models for guiding automated behavior by a UAV 100, for example, to understand and perform certain tasks. For example, image data (e.g., video) can be utilized to develop and train machine learning models such as trained neural networks. Utilizing such an approach, the navigation system of an autonomous UAV 100 can be configured to more effectively perform certain tasks, for example, based on training data in the form of video of the tasks being performed. For example, in a UAV 100 configured to perform a specific automated task such as inspecting a bridge, the navigation system may implement or apply a trained neural network based on video of previously performed inspections (of bridges or otherwise).

Models developed based on image training data can be incorporated or otherwise implemented in conjunction with developer-created applications and/or skills to configure the UAV 100 to perform certain tasks. For example, a developer may wish to create an application or skill for causing a UAV 100 to perform an inventory management task in a warehouse, for example, by autonomously flying around the warehouse, scanning inventory identifiers (e.g., barcodes), and communicating the scanned identifiers to some management process. Such an application or skill may rely on custom machine learning models that are not necessarily part of the underlying navigation system 120 of a UAV 100, but that rely on access to various perception inputs and the processing power of the navigation system 120.

FIG. 21 shows a flow diagram illustrating an example scenario for uploading a custom machine learning model to extend the functionality of the underlying navigation system 120 of a UAV 100. As shown in FIG. 21 , a developer may, using developer device 1806, upload a custom machine learning model 2100 to platform 2120. This custom machine learning model 2100 may include, for example, a pretrained model configured to perform some specific task. For example, if the developer is creating an application or skill specifically tailored to inspect bridges for cracks, the developer may pre-train a neural network model using image-based training data that is specifically tailored to detect cracks in structural objects based on captured images of the objects. The trained model may be configured to output image segmentation data distinguishing regions of a captured image that correspond to cracks and regions of the captured image not corresponding to cracks.

The custom machine learning model 2100 uploaded to the platform 1820 can be integrated into the navigation system 120 of a specific UAV 100 (or simulator thereof) to extend the capabilities of the system. For example, as shown in FIG. 21 , a navigation system 120 of the UAV 100 now includes both built in machine learning models 2120 as well as the custom machine learning model 2100 uploaded by the developer.

A developer-created application or skill may then access the outputs of the custom machine learning model 2100 to generate objective inputs that are fed back into the navigation system to guide autonomous behavior. For example, FIG. 22 shows a flow diagram illustrating an example process by which perception inputs (e.g., captured images) are fed into the machine learning models of the navigation system 120. In the example depicted in FIG. 22 , a custom machine learning model 2100 (e.g., a trained artificial neural network) produces machine learning model outputs 2204 (e.g., image segmentation) based on the perception inputs 2202. These machine learning model outputs 2204 are exposed to developer-created applications and//or skills 2230 via an API 2200 (e.g., similar to API 300 or 1500 discussed previously). The developer-created applications and/or skills 2230 can then produce objective inputs 2206 based on the machine learning model outputs 2204 that are fed into the navigation system 120 (e.g., via API 2200) to impact the autonomous behavior of the UAV 100.

The platform 1820 can also be utilized to train custom machine learning models based on training data uploaded by a developer. Artificial neural networks can be exposed to third-party developers, for example, via an API to received training data. For example, without developing or training their own machine leaning model, a developer can simply upload training data (e.g., in the form of labeled images) via an API to the platform 1820 where that training data is then utilized to train a machine learning model such as an artificial neural network to perform a certain task (e.g., detect cracks captured images of a bridge). For example, FIG. 23 shows a diagram that illustrates image-based training data for various tasks (e.g., capturing images at sporting events, bridge inspection, etc.) incorporated to train machine-learning models (e.g., based on artificial neural networks), for example, using an API 2300. Developer created applications and skills 2330 can then utilize the outputs of the trained machine learning models to guide the autonomous behavior of a UAV 100, for example, as described with respect to FIG. 22 . In this way, a developer can effectively plug into an artificial neural network, for example, through the use of an API, without having to develop such models on their own.

FIG. 24 shows a flow diagram illustrating an example scenario for uploading training data to platform 1820 to train a custom machine learning model to extend the functionality of the underlying navigation system 120 of a UAV 100. As shown in FIG. 24 , a developer may upload training data 2410 to platform 1820, for example via an API. The training data 2410 may include, for example, labeled images that can be used to train a machine learning model such as a neural network. A custom machine learning model 2400 is then trained at platform 1820 using the uploaded training data 2410. This custom machine learning model 2400 trained using the uploaded training data 2410 can then be integrated into the navigation system 120 of a specific UAV 100 (or simulator thereof) to extend the capabilities of the system. For example, as shown in FIG. 24 , a navigation system 120 of the UAV 100 now includes both built in machine learning models 2420 as well as the custom machine learning model 2400 generated at platform 1802 based on the uploaded training data 2410.

Post-Processing Outputs

In some embodiments, applications and/or skills can be developed to align outputs from the navigation system (e.g., precise orientation and attitude data about the UAV, obstacles, subjects, etc.) with image and/or video outputs from onboard image capture devices 114/115 in post processing. This can be utilized to produce various interesting post processing results such as frame bending, telemetry visualizations, event-based image processing transitions etc. An API can be configured to expose certain perception outputs from the navigation engine 120 that can be utilized by developer-created applications and/or skills for a variety of different post-processing features.

Application Store for Sharing Developer-Created Applications and/or Skills

As previously discussed, applications and skills created by third-party developers can be uploaded to platform 1820 for sharing or sale via an online application store 1850. Other users can then browse listings of available applications and/or skills that others have created and download selected applications and/or skills for simulation in a simulation environment and/or use with a real UAV 100. Users can comment on applications and/or skills while sharing them through the online storefront. Further, when uploading applications and/or skills for distribution via an online store 1850, developers can also upload images (e.g., video) captured when executing the created applications and/or skills using a device such as a UAV 100. In this way, other users can observe what to expect when using the uploaded application and/or skill.

In some embodiments, the online store 1850 may be regulated to maintain certain standards around the applications and/or skills created by developers. For example, the online store 1850 may include an automated framework that tests uploaded applications and/or skills (e.g., using a simulation environment) to ensure that the uploaded applications and/or skills at least do not interfere with the safe operation of a UAV 100. The automated framework may also screen uploaded applications and/or skills for other criteria such as compliance with applicable regulations, privacy concerns, etc.

Applications and/or Skills as a Learning and Verification Tool for Improving Autonomous Behavior

The results of simulation and implementation of applications and/or skills created by multiple developers may serve as a valuable dataset. The data may be used to improve the autonomous behavior of a UAV 100 and by extension user experiences, for example, through conducting studies and/or training machine learning processes. In some embodiments, a simulation environment (similar to as previously described) can be implemented as a verification tools to run large numbers of simulations of applications and/or skills created by other users. Data collected from the running of these simulations can be used, for example, to study and verify vehicle software integrity, perception changes, and/or improvements for future software updates.

An example machine learning application includes learning when users select certain skills in response to contextual factors such as information in captured images, position of tracked objects, semantic cues in the surrounding physical environment, or any other perceived feedback. Information learned through observing user selections of skills can in turn be used to guide the automatic selection of skills while a UAV is in flight based on any of the aforementioned factors. Another example machine learning application includes creating a skill that causes a specific type of motion or response and using data collected about the conditions in which users activate such skills to inform learned policies and/or modify certain parameters associated with the skill. For example, a skill to “squeeze through a gap” can be used to learn, based on perception, which objects in the physical world are safe to fly near. Such a specific skill may also be used to determine whether built-in obstacle avoidance behavior is configured too aggressively or conservatively.

Visual Outputs and User Interface Features Based on Skills

In some embodiments, skills can be configured to cause display of a visual output to user, for example, based on images captured from a UAV 100. FIG. 25 shows an example of a visual output 2502 displayed via a mobile device 104 in the form of a tablet display device. As indicated in FIG. 25 , the mobile device 104 may be communicatively coupled with a UAV 100 in flight through a physical environment 2500 via a wireless communication link 116. The UAV 100 autonomously navigates the physical environment based on one or more navigation objectives, for example, associated with an active skill, as previously discussed. The skill may further include instructions and/or assets configured to cause display of a visual output 2502 via the mobile device 104. The visual output 2502 may include a live video feed from an image capture device 114/115 onboard the UAV 100, recorded video from an image capture device 114/115 onboard the UAV 100, a rendering of a computer-generated model of the physical environment 2500 (e.g., based on data from the image capture device 114/115 and/or other sensors 112 onboard the UAV 100), and the like. As previously discussed, in some embodiments, a skill may include instructions and/or assets for processing captured images to apply imaging effects and/or other visualizations. For example, display output 2502 depicts a composite of a live video feed of the physical environment 2500 from the UAV 100 with added graphical elements (e.g., imaging effects, graphical overlays, interactive graphical interface features, etc.).

In some embodiments, a visual output based on a skill can include generated and displayed “augmentations.” Devices configured for augmented reality (AR devices) can deliver to a user a direct or indirect view of a physical environment which includes objects that are augmented (or supplemented) by computer-generated sensory outputs such as sound, video, graphics, or any other data that may augment (or supplement) a user's perception of the physical environment. For example, data gathered or generated by a tracking system 140 regarding a tracked object in the physical environment can be displayed to a user in the form of graphical overlays via an AR device while the UAV 100 is in flight through the physical environment and actively tracking the object and/or as an augmentation to video recorded by the UAV 100 after the flight has completed. Examples of AR devices that may be utilized to implement such functionality include smartphones, tablet computers, laptops, head mounted display devices (e.g., Microsoft HoloLens™, Google Glass™), virtual retinal display devices, heads up display (HUD) devices in vehicles, etc. For example, the previously mentioned mobile device 104 may be configured as an AR device. Note that for illustrative simplicity the term AR device is used herein to describe any type of device capable of presenting augmentations (visible, audible, tactile, etc.) to a user. The term “AR device” shall be understood to also include devices not commonly referred to as AR devices such as virtual reality (VR) headset devices (e.g., Oculus Rift™).

FIG. 26 shows an example view 2600 of a physical environment 2610 as presented at a display of an AR device. For example, the view 2600 may correspond with display 2502 presented via a mobile tablet device 104 as shown in FIG. 25 . The view 2600 of the physical environment 2610 shown in FIG. 26 may be generated based on images captured by one or more image capture devices 114/115 of a UAV 100 and be displayed to a user via the AR device in real-time or near-real-time as the UAV 100 is flying through the physical environment 2610 capturing the images. As shown in FIG. 26 , one or more augmentations may be presented to the user in the form of augmenting graphical overlays 2620 a, 2622 a, 2624 a, 2626 a, and 2620 b associated with objects (e.g., bikers 2640 a and 2640 b) in the physical environment 2610. For example, in an embodiment, the aforementioned augmenting graphical overlays may be generated and composited with video captured by UAV 100 as the UAV 100 tracks biker 2640 a. The composite including the captured video and the augmenting graphical overlays may be displayed to the user via a display of the AR device (e.g., a smartphone). In other embodiments, the AR device may include a transparent display (e.g., a head mounted display) through which the user can view the surrounding physical environment 2610. The transparent display may comprise a waveguide element made of a light-transmissive material through which projected images of one or more of the aforementioned augmenting graphical overlays are propagated and directed at the eyes of the user such that the projected images appear to the user to overlay the user's view of the physical environment 2610 and correspond with particular objects or points in the physical environment.

In some embodiments, augmentations may include labels with information associated with objects detected in the physical environment 2610. For example, FIG. 26 illustrates a scenario in which UAV 100 has detected and is tracking a first biker 2640 a and a second biker 2640 b. In response, one or more augmenting graphical overlays associated with the tracked objects may be displayed via the AR device at points corresponding to the locations of the bikers 2640 a-b as they appear in the captured image.

In some embodiments, augmentations may indicate specific object instances that are tracked by UAV 100. In the illustrative example provided in FIG. 26 , such augmentations are presented as augmenting graphical overlays 2620 a-b in the form of boxes that surround the specific object instances 2640 a-b (respectively). This is just an example provided for illustrative purposes. Indications of object instances may be presented using other types of augmentations (visual or otherwise).

In some embodiments, augmentations may include identifying information associated with detected objects. For example, augmenting graphical overlays 2622 a-b include names of the tracked bikers 2640 a-b (respectively). Further, augmenting graphical overlay 2622 a includes a picture of biker 2640 a. In some embodiments, information such as the picture of the biker 2640 a may be automatically pulled from an external source such as a social media platform (e.g., Facebook™ Twitter™, Instagram™, etc.). Although not shown in FIG. 26 , augmentations may also include avatars associated with identified people. Avatars may include 3D graphical reconstructions of the tracked person (e.g., based on captured images and other sensor data), generative “bitmoji” from instance segmentations, or any other type of generated graphics representative of tracked objects.

In some embodiments, augmentation may include information regarding an activity or state of the tracked object. For example, augmenting graphical overlay 2622 a includes information regarding the speed, distance traveled, and current heading of biker 2640 a. Other information regarding the activity of a tracked object may similarly be displayed.

In some embodiments, augmentations may include visual effects that track or interact with tracked objects. For example, FIG. 26 shows an augmenting graphical overlay 2624 a in the form of a projection of a 3D trajectory (e.g., current, past, and/or future) associated with biker 2640 a. In some embodiments, trajectories of multiple tracked objects may be presented as augmentations. Although not shown in FIG. 26 , augmentations may also include other visual effects such as halos, fireballs, dropped shadows, ghosting, multi-frame snapshots, etc.

Semantic knowledge of objects in the physical environment may also enable new AR user interaction paradigms. In other words, certain augmentations may be interactive and allow a user to control certain aspects of the flight of the UAV 100 and/or image capture by the UAV 100. Illustrative examples of interactive augmentations may include an interactive follow button that appears above moving objects. For example, in the scenario depicted in FIG. 26 , a UAV is tracking the motion of both bikers 2640 a and 2640 b, but is actively following (i.e., at a substantially constant separation distance) the first biker 2640 a. This is indicated in the augmenting graphical overlay 2622 a that states “currently following.” Note that a corresponding overlay 2622 b associated with the second biker 2640 b includes an interactive element (e.g., a “push to follow” button), that when pressed by a user, would cause the UAV 100 to stop following biker 2640 a and begin following biker 2640 b. Similarly, overlay 2622 a includes an interactive element (e.g., a “cancel” button), that when pressed by a user, would cause the UAV 100 to stop following biker 2640 a. In such a situation, the UAV 100 may revert to some default autonomous navigation objective, for example, following the path the bikers are traveling on but not any one biker in particular.

Other similar interactive augmentations may also be implemented. For example, although not shown in FIG. 26 , users may inspect certain objects, for example, by interacting with the visual depictions of the objects as presented by the AR device. For example, if the AR device includes a touch screen display, a user may cause the UAV 100 to follow the object simply by touching a region of the screen corresponding to the displayed object. This may also be applied to static objects that are not in motion. For example, by interacting with a region of the screen of an AR device corresponding to the displayed path 2650, an AR interface may display information regarding the path (e.g., source, destination, length, material, map overlay, etc.) or may cause the UAV to travel along the path at a particular altitude.

The size and geometry of detected objects may be taken into consideration when presenting augmentations. For example, in some embodiments, an interactive control element may be displayed as a ring about a detected object in an AR display. For example, FIG. 26 shows a control element 2626 a shown as a ring that appears to encircle the first biker 2340. The control element 2626 a may respond to user interactions to control an angle at which UAV 100 captures images of the biker 2640 a. For example, in a touch screen display context, a user may swipe their finger over the control element 2626 a to cause the UAV 100 to revolve about the biker 2640 a (e.g., at a substantially constant range) even as the biker 2640 a is in motion. Other similar interactive elements may be implemented to allow the user to zoom image captured in or out, pan from side to side, etc.

Using the developer console 1840 of platform 1820, developers can implement customized GUI features and other visual elements that are specific to their applications and/or skills. In some embodiments, a developer may adjust the GUI for a developed skill using simple feature toggles provided by the developer console 1840. For example, without having to build such GUI features from scratch, a developer may select from predefined GUI features such as sliders, checkboxes, and any other standard GUI features to enable user control over various parameters associated with a skill such as movement speed, distance to travel, etc. Further, developers can also send custom 3D models for rendering as augmentations, for example, as previously described.

Graphical UI features specific to a particular developer-created skill can integrate seamlessly with general GUI features associated with the UAV 100. FIG. 27 shows a series of screen captures illustrating how GUI features associated with a developer-created skill can be integrated into an application configured to control a UAV 100. The GUI depicted in FIG. 27 may be displayed as a graphical output from an application (e.g., application 1510) via a display screen (e.g., a touch-based display screen) of a computing device such as mobile device 104 (e.g., a user's tablet or smartphone).

Screen 2700 a depicts at menu interface element 2720 through which a user can select from multiple available skills. The available skills in this example include “boomerang,” “cablecam,” “follow,” “dronie,” “rocket,” and “spiral.” Each of the available skills may have been created by different developers including, for example, the developer of the application displaying the GUI and/or one or more other third-party developers.

Screen 2700 b depicts the GUI after selection of one of the available skills from menu 2720. As shown in screen 2700 b, the GUI may include a view 2710 of the physical environment, for example, generated based on images captured by one or more image capture devices 114/115 of the UAV 100. This view 2710 may comprise a live video feed from the one or more image capture devices 114/115 of the UAV 100. Screen 2700 b also depicts an augmented reality element 2730 specific to the selected skill. For example, a developer of the “cablecam” skill may have integrated 3D models to be displayed as overlays in the application GUI during execution of the skill. The augmentations 2730 in this example may comprise 3D models of waypoint indicators that are displayed via the GUI relative to specific locations in the physical environment. Notably, skill-specific GUI features such as augmentation 2730 are integrated seamlessly with other GUI features built into the underlying application. For example, built in GUI features such as the “stop” button 2740 are not specific to the “cablecam” skill and may be displayed regardless of the selected skill. Other GUI features such as the “return” button, settings menu, etc. may similarly be displayed regardless of the selected skill.

Screen 2700 c depicts another example GUI after selection of one of the available skills from menu 2720. As shown in screen 2700 c, the GUI still includes the view 2710 of the physical environment and various built in GUI features such as the stop button 2740. The GUI depicted in screen 2700 c further includes other skill-specific GUI features such as speed slider bar 2752, and a progress indicator 2754. Notably, while specific to the selected skill, the GUI elements 2752 and 2754 may be based on standard GUI elements provided for by the developer console 1840. In other words, to implement such elements in a given skill, the developer need only select certain predefined interactive elements to apply to certain objective parameters, for example, as defined by the skills SDK 1842. The developer would not be required to create custom visual assets to implement such GUI features. In the present example, the developer of the “cablecam” skill has defined the skill to display a slider bar 2752 to enable a user to control the “speed” objective parameter associated with the skill. In other words, when executing the “cablecam” skill, the UAV 100 will maneuver autonomously to approximate the motion of a cable camera while tracking a subject at a speed specified by a user via the slider bar element 2752.

As previously described, in some embodiments, skills can be shipped automatically and under-the-hood from a developer to an end-user application using a cloud configuration system 1860 of the platform 1820. A user of the application displaying the GUI of FIG. 27 may purchase or download a new skill such as the “cablecam” skill offered by a third-party developer. Purchased and/or downloaded skills may be seamlessly integrated into the existing application to extend the functionality of the application without needing to recompile or redownload the application. Skill-specific GUI elements, for example as described with respect to FIG. 27 , may appear within the existing application in response to purchasing, downloading, or otherwise accessing such skills.

Developers can also configure skills to utilize such perception outputs during post processing, for example, to add visual elements to captured video. For example, FIG. 28 shows an example visual output that includes 3D waypoint objects 2820 displayed as visual augmentations during execution of a skill for scanning a structure in an environment. The 3D waypoint objects 2820 may be overlaid on the view 2810 of the physical environment as displayed in a GUI of a mobile device 104 as the UAV 100 is performing the scan, for example, as described with respect to FIG. 27 . Further, perception outputs from the navigation system 120 (e.g., precise orientation and attitude data about the UAV, obstacles, subjects, etc.) can be accessed by the skill (e.g., via an API) to perform post processing on captured video to align the 3D waypoint objects 2820 with the captured video to produce a final composite video that includes the augmentations.

Auto-Return Functionality by an Autonomous UAV

A UAV 100 is configured to rely on several different systems to maintain tracking of a subject such as a human in the physical environment. For example, a UAV 100 may maintain visual tracking of a subject by processing images captured by image capture devices 114/115 onboard the UAV 100. If the tracked subject is carrying a device (e.g., mobile device 104) with localization capabilities, the UAV 100 may also track a location of that device, for example, by receiving location information (e.g., GPS data) from the device over a wireless link 116 (e.g., Wi-Fi).

During autonomous flight, certain situations may lead to a loss of visual contact between the UAV 100 and a tracked subject. For example, the view of the tracked subject from the UAV 100 may become occluded due to another object in the physical environment such as a tree. The image capture devices and/or associated computer vision processing systems onboard the UAV 100 may also experience failures which may lead to a loss of visual contact with the tracked subject. In any event, in some embodiments, the UAV 100 may be configured to seamlessly continue tracking and moving along with the subject by relying on other tracking systems if the UAV 100 loses visual contact with the subject.

In an example embodiment, in response to detecting a loss of visual tracking of a subject, the navigation system 120 onboard the UAV 100 may continue to track a location and movement of the subject based on signals received from another device in the physical environment. This other device may include, for example, a mobile device 104 held by the subject, another UAV in the vicinity that is currently tracking the subject, or any other device capable of determining information related to a location of the subject. For example, a mobile device equipped with a GPS receiver can resolve its location based on signals received from GPS satellites. The location of such a mobile device 104 may similarly be resolved using other localization techniques (e.g., cellular, Wi-Fi, etc.). Data regarding the location of the subject may be received by the UAV 100 from other devices (e.g., mobile device 104 or another UAV) over a wireless link such as Wi-Fi.

The navigation system 120 of the UAV may continue to cause the UAV 100 to fly a planned trajectory, for example, to follow the subject even after experiencing the loss of visual tracking by relying on the location information gathered by another device such as the mobile device 104 or another UAV. In this way, the UAV 100 may continue to maneuver seamlessly to track the subject until visual tracking can be re-established.

In some embodiments, while continuing to track and follow the subject after loss of visual tracking (e.g., using GPS from a mobile device), the navigation system 120 may cause the UAV 100 to perform one or more maneuvers aimed at re-establishing visual tracking of the subject. For example, assuming systems related to visual tracking are still functioning, the navigation system 120, may cause the UAV 100 to maneuver to avoid an occluding object (e.g., by descending, ascending, moving left/right, etc.) so that visual tracking can be re-established. These “corrective” maneuvers may be configured by the navigation system 120 to subtly change the trajectory of the UAV 100 to try to re-establish visual tracking while avoiding unnecessarily jarring or abrupt changes in trajectory that may lead to further subject tracking problems, less desirable captured video, etc.

In some embodiments, the navigation system 120 may adjust the extent to which corrective maneuvers are executed based on an elapsed time since visual tracking was lost. For example, the navigation system 120 may avoid any corrective maneuvers until a period of time since visual tracking was lost passes a first threshold. The navigation system 120 may then cause the UAV 100 to perform increasingly more drastic maneuvers as the period of time since visual tracking was lost passes subsequent thresholds. In some embodiments, such mitigating actions can be made user configurable, for example, based on inputs received via a mobile device 104.

Localization

A navigation system 120 of a UAV 100 may employ any number of other systems and techniques for localization. FIG. 29 shows an illustration of an example localization system 2900 that may be utilized to guide autonomous navigation of a vehicle such as UAV 100. In some embodiments, the positions and/or orientations of the UAV 100 and various other physical objects in the physical environment can be estimated using any one or more of the subsystems illustrated in FIG. 29 . By tracking changes in the positions and/or orientations over time (continuously or at regular or irregular time intervals (i.e., continually)), the motions (e.g., velocity, acceleration, etc.) of UAV 100 and other objects may also be estimated. Accordingly, any systems described herein for determining position and/or orientation may similarly be employed for estimating motion.

As shown in FIG. 29 , the example localization system 2900 may include the UAV 100, a global positioning system (GPS) comprising multiple GPS satellites 2902, a cellular system comprising multiple cellular antennae 2904 (with access to sources of localization data 2906), a Wi-Fi system comprising multiple Wi-Fi access points 2908 (with access to sources of localization data 1706), and/or a mobile device 104 operated by a user 106.

Satellite-based positioning systems such as GPS can provide effective global position estimates (within a few meters) of any device equipped with a receiver. For example, as shown in FIG. 29 , signals received at a UAV 100 from satellites of a GPS system 2902 can be utilized to estimate a global position of the UAV 100. Similarly, positions relative to other devices (e.g., a mobile device 104) can be determined by communicating (e.g., over a wireless communication link 116) and comparing the global positions of the other devices.

Localization techniques can also be applied in the context of various communications systems that are configured to transmit communications signals wirelessly. For example, various localization techniques can be applied to estimate a position of UAV 100 based on signals transmitted between the UAV 100 and any of cellular antennae 2904 of a cellular system or Wi-Fi access points 2908, 2910 of a Wi-Fi system. Known positioning techniques that can be implemented include, for example, time of arrival (ToA), time difference of arrival (TDoA), round trip time (RTT), angle of Arrival (AoA), and received signal strength (RSS). Moreover, hybrid positioning systems implementing multiple techniques such as TDoA and AoA, ToA and RSS, or TDoA and RSS can be used to improve the accuracy.

Some Wi-Fi standards, such as 802.11ac, allow for RF signal beamforming (i.e., directional signal transmission using phased-shifted antenna arrays) from transmitting Wi-Fi routers. Beamforming may be accomplished through the transmission of RF signals at different phases from spatially distributed antennas (a “phased antenna array”) such that constructive interference may occur at certain angles while destructive interference may occur at others, thereby resulting in a targeted directional RF signal field. Such a targeted field is illustrated conceptually in FIG. 29 by dotted lines 2912 emanating from Wi-Fi routers 2910.

An inertial measurement unit (IMU) may be used to estimate position and/or orientation of a device. An IMU is a device that measures a vehicle's angular velocity and linear acceleration. These measurements can be fused with other sources of information (e.g., those discussed above) to accurately infer velocity, orientation, and sensor calibrations. As described herein, a UAV 100 may include one or more IMUs. Using a method commonly referred to as “dead reckoning,” an IMU (or associated systems) may estimate a current position based on previously measured positions using measured accelerations and the time elapsed from the previously measured positions. While effective to an extent, the accuracy achieved through dead reckoning based on measurements from an IMU quickly degrades due to the cumulative effect of errors in each predicted current position. Errors are further compounded by the fact that each predicted position is based on a calculated integral of the measured velocity. To counter such effects, an embodiment utilizing localization using an IMU may include localization data from other sources (e.g., the GPS, Wi-Fi, and cellular systems described above) to continually update the last known position and/or orientation of the object. Further, a nonlinear estimation algorithm (one embodiment being an “extended Kalman filter”) may be applied to a series of measured positions and/or orientations to produce a real-time prediction of the current position and/or orientation based on assumed uncertainties in the observed data. Kalman filters are commonly applied in the area of aircraft navigation, guidance, and controls.

Computer vision may be used to estimate the position and/or orientation of a capturing camera (and by extension a device to which the camera is coupled) as well as other objects in the physical environment. The term, “computer vision” in this context may generally refer to any method of acquiring, processing, analyzing and “understanding” captured images. Computer vision may be used to estimate position and/or orientation using a number of different methods. For example, in some embodiments, raw image data received from one or more image capture devices (onboard or remote from the UAV 100) may be received and processed to correct for certain variables (e.g., differences in camera orientation and/or intrinsic parameters (e.g., lens variations)). As previously discussed with respect to FIG. 1A, the UAV 100 may include two or more image capture devices 114/115. By comparing the captured image from two or more vantage points (e.g., at different time steps from an image capture device in motion), a system employing computer vision may calculate estimates for the position and/or orientation of a vehicle on which the image capture device is mounted (e.g., UAV 100) and/or of captured objects in the physical environment (e.g., a tree, building, etc.).

Computer vision can be applied to estimate position and/or orientation using a process referred to as “visual odometry.” FIG. 30 illustrates the working concept behind visual odometry at a high level. A plurality of images are captured in sequence as an image capture device moves through space. Due to the movement of the image capture device, the images captured of the surrounding physical environment change from frame to frame. In FIG. 30 , this is illustrated by initial image capture FOV 3052 and a subsequent image capture FOV 3054 captured as the image capture device has moved from a first position to a second position over a period of time. In both images, the image capture device may capture real world physical objects, for example, the house 3080 and/or the person 3002. Computer vision techniques are applied to the sequence of images to detect and match features of physical objects captured in the FOV of the image capture device. For example, a system employing computer vision may search for correspondences in the pixels of digital images that have overlapping FOV. The correspondences may be identified using a number of different methods such as correlation-based and feature-based methods. As shown in, in FIG. 30 , features such as the head of a human subject 3002 or the corner of the chimney on the house 3080 can be identified, matched, and thereby tracked. By incorporating sensor data from an IMU (or accelerometer(s) or gyroscope(s)) associated with the image capture device to the tracked features of the image capture, estimations may be made for the position and/or orientation of the image capture relative to the objects 3080, 3002 captured in the images. Further, these estimates can be used to calibrate various other systems, for example, through estimating differences in camera orientation and/or intrinsic parameters (e.g., lens variations) or IMU biases and/or orientation. Visual odometry may be applied at both the UAV 100 and any other computing device such as a mobile device 104 to estimate the position and/or orientation of the UAV 100 and/or other objects. Further, by communicating the estimates between the systems (e.g., via a wireless communication link 116) estimates may be calculated for the respective positions and/or orientations relative to each other. Position and/or orientation estimates based in part on sensor data from an on board IMU may introduce error propagation issues. As previously stated, optimization techniques may be applied to such estimates to counter uncertainties. In some embodiments, a nonlinear estimation algorithm (one embodiment being an “extended Kalman filter”) may be applied to a series of measured positions and/or orientations to produce a real-time optimized prediction of the current position and/or orientation based on assumed uncertainties in the observed data. Such estimation algorithms can be similarly applied to produce smooth motion estimations.

In some embodiments, data received from sensors onboard UAV 100 can be processed to generate a 3D map of the surrounding physical environment while estimating the relative positions and/or orientations of the UAV 100 and/or other objects within the physical environment. This process is sometimes referred to as simultaneous localization and mapping (SLAM). In such embodiments, using computer vision processing, a system in accordance with the present teaching can search for dense correspondence between images with overlapping FOV (e.g., images taken during sequential time steps and/or stereoscopic images taken at the same time step). The system can then use the dense correspondences to estimate a depth or distance to each pixel represented in each image. These depth estimates can then be used to continually update a generated 3D model of the physical environment taking into account motion estimates for the image capture device (i.e., UAV 100) through the physical environment.

In some embodiments, a 3D model of the surrounding physical environment may be generated as a 3D occupancy map that includes multiple voxels with each voxel corresponding to a 3D volume of space in the physical environment that is at least partially occupied by a physical object. For example, FIG. 31 shows an example view of a 3D occupancy map 3102 of a physical environment including multiple cubical voxels. Each of the voxels in the 3D occupancy map 3102 correspond to a space in the physical environment that is at least partially occupied by a physical object. A navigation system 120 of a UAV 100 can be configured to navigate the physical environment by planning a 3D trajectory 3120 through the 3D occupancy map 3102 that avoids the voxels. In some embodiments, this 3D trajectory 3120 (planned using the 3D occupancy map 3102) can be updated by applying an image space motion planning process. In such an embodiment, the planned 3D trajectory 3120 of the UAV 100 is projected into an image space of captured images for analysis relative to certain identified high cost regions (e.g., regions having invalid depth estimates).

Computer vision may also be applied using sensing technologies other than cameras, such as light detection and ranging (LIDAR) technology. For example, a UAV 100 equipped with LIDAR may emit one or more laser beams in a scan up to 360 degrees around the UAV 100. Light received by the UAV 100 as the laser beams reflect off physical objects in the surrounding physical world may be analyzed to construct a real time 3D computer model of the surrounding physical world. Depth sensing through the use of LIDAR may in some embodiments augment depth sensing through pixel correspondence as described earlier. Further, images captured by cameras (e.g., as described earlier) may be combined with the laser constructed 3D models to form textured 3D models that may be further analyzed in real time or near real time for physical object recognition (e.g., by using computer vision algorithms).

The computer vision-aided localization techniques described above may calculate the position and/or orientation of objects in the physical world in addition to the position and/or orientation of the UAV 100. The estimated positions and/or orientations of these objects may then be fed into a motion planning system 130 of the navigation system 120 to plan paths that avoid obstacles while satisfying certain objectives (e.g., as previously described). In addition, in some embodiments, a navigation system 120 may incorporate data from proximity sensors (e.g., electromagnetic, acoustic, and/or optics based) to estimate obstacle positions with more accuracy. Further refinement may be possible with the use of stereoscopic computer vision with multiple cameras, as described earlier.

The localization system 2900 of FIG. 29 (including all of the associated subsystems as previously described) is only one example of a system configured to estimate positions and/or orientations of a UAV 100 and other objects in the physical environment. A localization system 2900 may include more or fewer components than shown, may combine two or more components, or may have a different configuration or arrangement of the components. Some of the various components shown in FIG. 29 may be implemented in hardware, software or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits.

Object Tracking

A UAV 100 can be configured to track one or more objects, for example, to enable intelligent autonomous flight. The term “objects” in this context can include any type of physical object occurring in the physical world. Objects can include dynamic objects such as a people, animals, and other vehicles. Objects can also include static objects such as landscape features, buildings, and furniture. Further, certain descriptions herein may refer to a “subject” (e.g., human subject 102). The terms “subject” as used in this disclosure may simply refer to an object being tracked using any of the disclosed techniques. The terms “object” and “subject” may therefore be used interchangeably.

With reference to FIG. 2 , a tracking system 140 associated with a UAV 100 can be configured to track one or more physical objects based on images of the objects captured by image capture devices (e.g., image capture devices 114 and/or 115) onboard the UAV 100. While a tracking system 140 can be configured to operate based only on input from image capture devices, the tracking system 140 can also be configured to incorporate other types of information to aid in the tracking.

In some embodiments, a tracking system 140 can be configured to fuse information pertaining to two primary categories: semantics and 3D geometry. As images are received, the tracking system 140 may extract semantic information regarding certain objects captured in the images based on an analysis of the pixels in the images. Semantic information regarding a captured object can include information such as an object's category (i.e., class), location, shape, size, scale, pixel segmentation, orientation, inter-class appearance, activity, and pose. In an example embodiment, the tracking system 140 may identify general locations and categories of objects based on captured images and then determine or infer additional more detailed information about individual instances of objects based on further processing. Such a process may be performed as a sequence of discrete operations, a series of parallel operations, or as a single operation. For example, FIG. 32 shows an example image 3220 captured by a UAV in flight through a physical environment. As shown in FIG. 32 , the example image 3220 includes captures of two physical objects, specifically, two people present in the physical environment. The example image 3220 may represent a single frame in a series of frames of video captured by the UAV. A tracking system 140 may first identify general locations of the captured objects in the image 3220. For example, pixel map 3230 shows two dots corresponding to the general locations of the captured objects in the image. These general locations may be represented as image coordinates. The tracking system 140 may further process the captured image 3220 to determine information about the individual instances of the captured objects. For example, pixel map 3240 shows a result of additional processing of image 3220 identifying pixels corresponding to the individual object instances (i.e., people in this case). Semantic cues can be used to locate and identify objects in captured images as well as associate identified objects occurring in multiple images. For example, as previously mentioned, the captured image 3220 depicted in FIG. 32 may represent a single frame in a sequence of frames of a captured video. Using semantic cues, a tracking system 140 may associate regions of pixels captured in multiple images as corresponding to the same physical object occurring in the physical environment.

In some embodiments, a tracking system 140 can be configured to utilize 3D geometry of identified objects to associate semantic information regarding the objects based on images captured from multiple views in the physical environment. Images captured from multiple views may include images captured by multiple image capture devices having different positions and/or orientations at a single time instant. For example, each of the image capture devices 114 shown mounted to a UAV 100 in FIG. 1A may include cameras at slightly offset positions (to achieve stereoscopic capture). Further, even if not individually configured for stereoscopic image capture, the multiple image capture devices 114 may be arranged at different positions relative to the UAV 100, for example, as shown in FIG. 1A. Images captured from multiple views may also include images captured by an image captured device at multiple time instants as the image capture device moves through the physical environment. For example, any of the image capture devices 114 and/or 115 mounted to UAV 100 will individually capture images from multiple views as the UAV 100 moves through the physical environment.

Using an online visual-inertial state estimation system, a tracking system 140 can determine or estimate a trajectory of the UAV 100 as it moves through the physical environment. Thus, the tracking system 140 can associate semantic information in captured images, such as locations of detected objects, with information about the 3D trajectory of the objects, using the known or estimated 3D trajectory of the UAV 100. For example, FIG. 33 shows a trajectory 3310 of a UAV 100 moving through a physical environment. As the UAV 100 moves along trajectory 3310, the one or more image capture devices (e.g., devices 114 and/or 115) capture images of the physical environment at multiple views 3312 a-c. Included in the images at multiple views 3312 a-c are captures of an object such as a human subject 102. By processing the captured images at multiple views 3312 a-c, a trajectory 3320 of the object can also be resolved.

Object detections in captured images create rays from a center position of a capturing camera to the object along which the object lies, with some uncertainty. The tracking system 140 can compute depth measurements for these detections, creating a plane parallel to a focal plane of a camera along which the object lies, with some uncertainty. These depth measurements can be computed by a stereo vision algorithm operating on pixels corresponding with the object between two or more camera images at different views. The depth computation can look specifically at pixels that are labeled to be part of an object of interest (e.g., a subject 102). The combination of these rays and planes over time can be fused into an accurate prediction of the 3D position and velocity trajectory of the object over time.

While a tracking system 140 can be configured to rely exclusively on visual data from image capture devices onboard a UAV 100, data from other sensors (e.g., sensors on the object, on the UAV 100, or in the environment) can be incorporated into this framework when available. Additional sensors may include GPS, IMU, barometer, magnetometer, and cameras at other devices such as a mobile device 104. For example, a GPS signal from a mobile device 104 held by a person can provide rough position measurements of the person that are fused with the visual information from image capture devices onboard the UAV 100. An IMU sensor at the UAV 100 and/or a mobile device 104 can provide acceleration and angular velocity information, a barometer can provide relative altitude, and a magnetometer can provide heading information. Images captured by cameras at a mobile device 104 held by a person can be fused with images from cameras onboard the UAV 100 to estimate relative pose between the UAV 100 and the person by identifying common features captured in the images.

In some embodiments, data from various sensors are input into a spatiotemporal factor graph to probabilistically minimize total measurement error. FIG. 34 shows a diagrammatic representation of an example spatiotemporal factor graph 3400 that can be used to estimate a 3D trajectory of an object (e.g., including pose and velocity over time). In the example spatiotemporal factor graph 3400 depicted in FIG. 34 , variable values such as the pose and velocity (represented as nodes (3402 and 3404 respectively)) connected by one or more motion model processes (represented as nodes 3406 along connecting edges). For example, an estimate or prediction for the pose of the UAV 100 and/or other object at time step 1 (i.e., variable X(1)) may be calculated by inputting estimated pose and velocity at a prior time step (i.e., variables X(0) and V(0)) as well as various perception inputs such as stereo depth measurements and camera image measurements via one or more motion models. A spatiotemporal factor model can be combined with an outlier rejection mechanism wherein measurements deviating too far from an estimated distribution are thrown out. In order to estimate a 3D trajectory from measurements at multiple time instants, one or more motion models (or process models) are used to connect the estimated variables between each time step in the factor graph. Such motion models can include any one of constant velocity, zero velocity, decaying velocity, and decaying acceleration. Applied motion models may be based on a classification of a type of object being tracked and/or learned using machine learning techniques. For example, a cyclist is likely to make wide turns at speed, but is not expected to move sideways. Conversely, a small animal such as a dog may exhibit a more unpredictable motion pattern.

In some embodiments, a tracking system 140 can generate an intelligent initial estimate for where a tracked object will appear in a subsequently captured image based on a predicted 3D trajectory of the object. FIG. 35 shows a diagram that illustrates this concept. As shown in FIG. 35 , a UAV 100 is moving along a trajectory 3510 while capturing images of the surrounding physical environment, including of a human subject 102. As the UAV 100 moves along the trajectory 3510, multiple images (e.g., frames of video) are captured from one or more mounted image capture devices 114/115. FIG. 35 shows a first FOV of an image capture device at a first pose 3540 and a second FOV of the image capture device at a second pose 3542. In this example, the first pose 3540 may represent a previous pose of the image capture device at a time instant t(0) while the second pose 3542 may represent a current pose of the image capture device at a time instant t(1). At time instant t(0), the image capture device captures an image of the human subject 102 at a first 3D position 3560 in the physical environment. This first position 3560 may be the last known position of the human subject 102. Given the first pose 3540 of the image capture device, the human subject 102 while at the first 3D position 3560 appears at a first image position 3550 in the captured image. An initial estimate for a second (or current) image position 3552 can therefore be made based on projecting a last known 3D trajectory 3520 a of the human subject 102 forward in time using one or more motion models associated with the object. For example, predicted trajectory 3520 b shown in FIG. 35 represents this projection of the 3D trajectory 3520 a forward in time. A second 3D position 3562 (at time t(1)) of the human subject 102 along this predicted trajectory 3520 b can then be calculated based on an amount of time elapsed from t(0) to t(1). This second 3D position 3562 can then be projected into the image plane of the image capture device at the second pose 3542 to estimate the second image position 3552 that will correspond to the human subject 102. Generating such an initial estimate for the position of a tracked object in a newly captured image narrows down the search space for tracking and enables a more robust tracking system, particularly in the case of a UAV 100 and/or tracked object that exhibits rapid changes in position and/or orientation.

In some embodiments, the tracking system 140 can take advantage of two or more types of image capture devices onboard the UAV 100. For example, as previously described with respect to FIG. 1A, the UAV 100 may include image capture device 114 configured for visual navigation as well as an image captured device 115 for capturing images that are to be viewed. The image capture devices 114 may be configured for low-latency, low-resolution, and high FOV, while the image capture device 115 may be configured for high resolution. An array of image capture devices 114 about a perimeter of the UAV 100 can provide low-latency information about objects up to 360 degrees around the UAV 100 and can be used to compute depth using stereo vision algorithms. Conversely, the other image capture device 115 can provide more detailed images (e.g., high resolution, color, etc.) in a limited FOV.

Combining information from both types of image capture devices 114 and 115 can be beneficial for object tracking purposes in a number of ways. First, the high-resolution color information from an image capture device 115 can be fused with depth information from the image capture devices 114 to create a 3D representation of a tracked object. Second, the low-latency of the image capture devices 114 can enable more accurate detection of objects and estimation of object trajectories. Such estimates can be further improved and/or corrected based on images received from a high-latency, high resolution image capture device 115. The image data from the image capture devices 114 can either be fused with the image data from the image capture device 115, or can be used purely as an initial estimate.

By using the image capture devices 114, a tracking system 140 can achieve tracking of objects up to 360 degrees around the UAV 100. The tracking system 140 can fuse measurements from any of the image capture devices 114 or 115 when estimating a relative position and/or orientation of a tracked object as the positions and orientations of the image capture devices 114 and 115 change over time. The tracking system 140 can also orient the image capture device 115 to get more accurate tracking of specific objects of interest, fluidly incorporating information from both image capture modalities. Using knowledge of where all objects in the scene are, the UAV 100 can exhibit more intelligent autonomous flight.

As previously discussed, the high-resolution image capture device 115 may be mounted to an adjustable mechanism such as a gimbal that allows for one or more degrees of freedom of motion relative to the body of the UAV 100. Such a configuration is useful in stabilizing image capture as well as tracking objects of particular interest. An active gimbal mechanism configured to adjust an orientation of a higher-resolution image capture device 115 relative to the UAV 100 so as to track a position of an object in the physical environment may allow for visual tracking at greater distances than may be possible through use of the lower-resolution image capture devices 114 alone. Implementation of an active gimbal mechanism may involve estimating the orientation of one or more components of the gimbal mechanism at any given time. Such estimations may be based on any of hardware sensors coupled to the gimbal mechanism (e.g., accelerometers, rotary encoders, etc.), visual information from the image capture devices 114/115, or a fusion based on any combination thereof.

A tracking system 140 may include an object detection system for detecting and tracking various objects. Given one or more classes of objects (e.g., humans, buildings, cars, animals, etc.), the object detection system may identify instances of the various classes of objects occurring in captured images of the physical environment. Outputs by the object detection system can be parameterized in a few different ways. In some embodiments, the object detection system processes received images and outputs a dense per-pixel segmentation, where each pixel is associated with a value corresponding to either an object class label (e.g., human, building, car, animal, etc.) and/or a likelihood of belonging to that object class. For example, FIG. 36 shows a visualization 3604 of a dense per-pixel segmentation of a captured image 3602 where pixels corresponding to detected objects 3610 a-b classified as humans are set apart from all other pixels in the image 3602. Another parameterization may include resolving the image location of a detected object to a particular image coordinate (e.g., as shown at map 3230 in FIG. 32 ), for example, based on centroid of the representation of the object in a received image.

In some embodiments, the object detection system can utilize a deep convolutional neural network for object detection. For example, the input may be a digital image (e.g., image 3602), and the output may be a tensor with the same spatial dimension. Each slice of the output tensor may represent a dense segmentation prediction, where each pixel's value is proportional to the likelihood of that pixel belonging to the class of object corresponding to the slice. For example, the visualization 3604 shown in FIG. 36 may represent a particular slice of the aforementioned tensor where each pixel's value is proportional to the likelihood that the pixel corresponds with a human. In addition, the same deep convolutional neural network can also predict the centroid locations for each detected instance, as described in the following section.

A tracking system 140 may also include an instance segmentation system for distinguishing between individual instances of objects detected by the object detection system. In some embodiments, the process of distinguishing individual instances of detected objects may include processing digital images captured by the UAV 100 to identify pixels belonging to one of a plurality of instances of a class of physical objects present in the physical environment and captured in the digital images. As previously described with respect to FIG. 36 , a dense per-pixel segmentation algorithm can classify certain pixels in an image as corresponding to one or more classes of objects. This segmentation process output may allow a tracking system 140 to distinguish the objects represented in an image and the rest of the image (i.e., a background). For example, the visualization 3604 distinguishes pixels that correspond to humans (e.g., included in region 3612) from pixels that do not correspond to humans (e.g., included in region 3630). However, this segmentation process does not necessarily distinguish between individual instances of the detected objects. A human viewing the visualization 3604 may conclude that the pixels corresponding to humans in the detected image actually correspond to two separate humans; however, without further analysis, a tracking system 140 may be unable to make this distinction.

Effective object tracking may involve distinguishing pixels that correspond to distinct instances of detected objects. This process is known as “instance segmentation.” FIG. 37 shows an example visualization 3704 of an instance segmentation output based on a captured image 3702. Similar to the dense per-pixel segmentation process described with respect to FIG. 36 , the output represented by visualization 3704 distinguishes pixels (e.g., included in regions 3712 a-c) that correspond to detected objects 3710 a-c of a particular class of objects (in this case humans) from pixels that do not correspond to such objects (e.g., included in region 3730). Notably, the instance segmentation process goes a step further to distinguish pixels corresponding to individual instances of the detected objects from each other. For example, pixels in region 3712 a correspond to a detected instance of a human 3710 a, pixels in region 3712 b correspond to a detected instance of a human 3710 b, and pixels in region 3712 c correspond to a detected instance of a human 3710 c.

Distinguishing between instances of detected objects may be based on an analysis of pixels corresponding to detected objects. For example, a grouping method may be applied by the tracking system 140 to associate pixels corresponding to a particular class of object to a particular instance of that class by selecting pixels that are substantially similar to certain other pixels corresponding to that instance, pixels that are spatially clustered, pixel clusters that fit an appearance-based model for the object class, etc. Again, this process may involve applying a deep convolutional neural network to distinguish individual instances of detected objects.

Instance segmentation may associate pixels corresponding to particular instances of objects; however, such associations may not be temporally consistent. Consider again, the example described with respect to FIG. 37 . As illustrated in FIG. 37 , a tracking system 140 has identified three instances of a certain class of objects (i.e., humans) by applying an instance segmentation process to a captured image 3702 of the physical environment. This example captured image 3702 may represent only one frame in a sequence of frames of captured video. When a second frame is received, the tracking system 140 may not be able to recognize newly identified object instances as corresponding to the same three people 3710 a-c as captured in image 3702.

To address this issue, the tracking system 140 can include an identity recognition system. An identity recognition system may process received inputs (e.g., captured images) to learn the appearances of instances of certain objects (e.g., of particular people). Specifically, the identity recognition system may apply a machine-learning appearance-based model to digital images captured by one or more image capture devices 114/115 associated with a UAV 100. Instance segmentations identified based on processing of captured images can then be compared against such appearance-based models to resolve unique identities for one or more of the detected objects.

Identity recognition can be useful for various different tasks related to object tracking. As previously alluded to, recognizing the unique identities of detected objects allows for temporal consistency. Further, identity recognition can enable the tracking of multiple different objects (as will be described in more detail). Identity recognition may also facilitate object persistence that enables re-acquisition of previously tracked objects that fell out of view due to limited FOV of the image capture devices, motion of the object, and/or occlusion by another object. Identity recognition can also be applied to perform certain identity-specific behaviors or actions, such as recording video when a particular person is in view.

In some embodiments, an identity recognition process may employ a deep convolutional neural network to learn one or more effective appearance-based models for certain objects. In some embodiments, the neural network can be trained to learn a distance metric that returns a low distance value for image crops belonging to the same instance of an object (e.g., a person), and a high distance value otherwise.

In some embodiments, an identity recognition process may also include learning appearances of individual instances of objects such as people. When tracking humans, a tracking system 140 may be configured to associate identities of the humans, either through user-input data or external data sources such as images associated with individuals available on social media. Such data can be combined with detailed facial recognition processes based on images received from any of the one or more image capture devices 114/115 onboard the UAV 100. In some embodiments, an identity recognition process may focus on one or more key individuals. For example, a tracking system 140 associated with a UAV 100 may specifically focus on learning the identity of a designated owner of the UAV 100 and retain and/or improve its knowledge between flights for tracking, navigation, and/or other purposes such as access control.

In some embodiments, a tracking system 140 may be configured to focus tracking on a specific object detected in captured images. In such a single-object tracking approach, an identified object (e.g., a person) is designated for tracking while all other objects (e.g., other people, trees, buildings, landscape features, etc.) are treated as distractors and ignored. While useful in some contexts, a single-object tracking approach may have some disadvantages. For example, an overlap in trajectory, from the point of view of an image capture device, of a tracked object and a distractor object may lead to an inadvertent switch in the object being tracked such that the tracking system 140 begins tracking the distractor instead. Similarly, spatially close false positives by an object detector can also lead to inadvertent switches in tracking.

A multi-object tracking approach addresses these shortcomings, and introduces a few additional benefits. In some embodiments, a unique track is associated with each object detected in the images captured by the one or more image capture devices 114/115. In some cases, it may not be practical, from a computing standpoint, to associate a unique track with every single object that is captured in the images. For example, a given image may include hundreds of objects, including minor features such as rocks or leaves of trees. Instead, unique tracks may be associate with certain classes of objects that may be of interest from a tracing standpoint. For example, the tracking system 140 may be configured to associate a unique track with every object detected that belongs to a class that is generally mobile (e.g., people, animals, vehicles, etc.).

Each unique track may include an estimate for the spatial location and movement of the object being tracked (e.g., using the spatiotemporal factor graph described earlier) as well as its appearance (e.g., using the identity recognition feature). Instead of pooling together all other distractors (i.e., as may be performed in a single object tracking approach), the tracking system 140 can learn to distinguish between the multiple individual tracked objects. By doing so, the tracking system 140 may render inadvertent identity switches less likely. Similarly, false positives by the object detector can be more robustly rejected as they will tend to not be consistent with any of the unique tracks.

An aspect to consider when performing multi-object tracking includes the association problem. In other words, given a set of object detections based on captured images (including parameterization by 3D location and regions in the image corresponding to segmentation), an issue arises regarding how to associate each of the set of object detections with corresponding tracks. To address the association problem, the tracking system 140 can be configured to associate one of a plurality of detected objects with one of a plurality of estimated object tracks based on a relationship between a detected object and an estimate object track. Specifically, this process may involve computing a “cost” value for one or more pairs of object detections and estimate object tracks. The computed cost values can take into account, for example, the spatial distance between a current location (e.g., in 3D space and/or image space) of a given object detection and a current estimate of a given track (e.g., in 3D space and/or in image space), an uncertainty of the current estimate of the given track, a difference between a given detected object's appearance and a given track's appearance estimate, and/or any other factors that may tend to suggest an association between a given detected object and given track. In some embodiments, multiple cost values are computed based on various different factors and fused into a single scalar value that can then be treated as a measure of how well a given detected object matches a given track. The aforementioned cost formulation can then be used to determine an optimal association between a detected object and a corresponding track by treating the cost formulation as an instance of a minimum cost perfect bipartite matching problem, which can be solved using, for example, the Hungarian algorithm.

In some embodiments, effective object tracking by a tracking system 140 may be improved by incorporating information regarding a state of an object. For example, a detected object such as a human may be associated with any one or more defined states. A state in this context may include an activity by the object such as sitting, standing, walking, running, or jumping. In some embodiments, one or more perception inputs (e.g., visual inputs from image capture devices 114/115) may be used to estimate one or more parameters associated with detected objects. The estimated parameters may include an activity type, motion capabilities, trajectory heading, contextual location (e.g., indoors vs. outdoors), interaction with other detected objects (e.g., two people walking together, a dog on a leash held by a person, a trailer pulled by a car, etc.), and any other semantic attributes.

Generally, object state estimation may be applied to estimate one or more parameters associated with a state of a detected object based on perception inputs (e.g., images of the detected object captured by one or more image capture devices 114/115 onboard a UAV 100 or sensor data from any other sensors onboard the UAV 100). The estimated parameters may then be applied to assist in predicting the motion of the detected object and thereby assist in tracking the detected object. For example, future trajectory estimates may differ for a detected human depending on whether the detected human is walking, running, jumping, riding a bicycle, riding in a car, etc. In some embodiments, deep convolutional neural networks may be applied to generate the parameter estimates based on multiple data sources (e.g., the perception inputs) to assist in generating future trajectory estimates and thereby assist in tracking.

As previously alluded to, a tracking system 140 may be configured to estimate (i.e., predict) a future trajectory of a detected object based on past trajectory measurements and/or estimates, current perception inputs, motion models, and any other information (e.g., object state estimates). Predicting a future trajectory of a detected object is particularly useful for autonomous navigation by the UAV 100. Effective autonomous navigation by the UAV 100 may depend on anticipation of future conditions just as much as current conditions in the physical environment. Through a motion planning process, a navigation system of the UAV 100 may generate control commands configured to cause the UAV 100 to maneuver, for example, to avoid a collision, maintain separation with a tracked object in motion, and/or satisfy any other navigation objectives.

Predicting a future trajectory of a detected object is generally a relatively difficult problem to solve. The problem can be simplified for objects that are in motion according to a known and predictable motion model. For example, an object in free fall is expected to continue along a previous trajectory while accelerating at rate based on a known gravitational constant and other known factors (e.g., wind resistance). In such cases, the problem of generating a prediction of a future trajectory can be simplified to merely propagating past and current motion according to a known or predictable motion model associated with the object. Objects may of course deviate from a predicted trajectory generated based on such assumptions for a number of reasons (e.g., due to collision with another object). However, the predicted trajectories may still be useful for motion planning and/or tracking purposes.

Dynamic objects such as people and animals, present a more difficult challenge when predicting future trajectories because the motion of such objects is generally based on the environment and their own free will. To address such challenges, a tracking system 140 may be configured to take accurate measurements of the current position and motion of an object and use differentiated velocities and/or accelerations to predict a trajectory a short time (e.g., seconds) into the future and continually update such prediction as new measurements are taken. Further, the tracking system 140 may also use semantic information gathered from an analysis of captured images as cues to aid in generating predicted trajectories. For example, a tracking system 140 may determine that a detected object is a person on a bicycle traveling along a road. With this semantic information, the tracking system 140 may form an assumption that the tracked object is likely to continue along a trajectory that roughly coincides with a path of the road. As another related example, the tracking system 140 may determine that the person has begun turning the handlebars of the bicycle to the left. With this semantic information, the tracking system 140 may form an assumption that the tracked object will likely turn to the left before receiving any positional measurements that expose this motion. Another example, particularly relevant to autonomous objects such as people or animals is to assume that that the object will tend to avoid collisions with other objects. For example, the tracking system 140 may determine a tracked object is a person heading on a trajectory that will lead to a collision with another object such as a light pole. With this semantic information, the tracking system 140 may form an assumption that the tracked object is likely to alter its current trajectory at some point before the collision occurs. A person having ordinary skill will recognize that these are only examples of how semantic information may be utilized as a cue to guide prediction of future trajectories for certain objects.

In addition to performing an object detection process in one or more captured images per time frame, the tracking system 140 may also be configured to perform a frame-to-frame tracking process, for example, to detect motion of a particular set or region of pixels in images at subsequent time frames (e.g., video frames). Such a process may involve applying a mean-shift algorithm, a correlation filter, and/or a deep network. In some embodiments, frame-to-frame tracking may be applied by a system that is separate from an object detection system wherein results from the frame-to-frame tracking are fused into a spatiotemporal factor graph. Alternatively, or in addition, an object detection system may perform frame-to-frame tracking if, for example, the system has sufficient available computing resources (e.g., memory). For example, an object detection system may apply frame-to-frame tracking through recurrence in a deep network and/or by passing in multiple images at a time. A frame-to-frame tracking process and object detection process can also be configured to complement each other, with one resetting the other when a failure occurs.

As previously discussed, the tracking system 140 may be configured to process images (e.g., the raw pixel data) received from one or more image capture devices 114/115 onboard a UAV 100. Alternatively, or in addition, the tracking system 140 may also be configured to operate by processing disparity images. A “disparity image” may generally be understood as an image representative of a disparity between two or more corresponding images. For example, a stereo pair of images (e.g., left image and right image) captured by a stereoscopic image capture device will exhibit an inherent offset due to the slight difference in position of the two or more cameras associated with the stereoscopic image capture device. Despite the offset, at least some of the objects appearing in one image should also appear in the other image; however, the image locations of pixels corresponding to such objects will differ. By matching pixels in one image with corresponding pixels in the other and calculating the distance between these corresponding pixels, a disparity image can be generated with pixel values that are based on the distance calculations. Such a disparity image will tend to highlight regions of an image that correspond to objects in the physical environment since the pixels corresponding to the object will have similar disparities due to the object's 3D location in space. Accordingly, a disparity image, that may have been generated by processing two or more images according to a separate stereo algorithm, may provide useful cues to guide the tracking system 140 in detecting objects in the physical environment. In many situations, particularly where harsh lighting is present, a disparity image may actually provide stronger cues about the location of objects than an image captured from the image capture devices 114/115. As mentioned, disparity images may be computed with a separate stereo algorithm. Alternatively, or in addition, disparity images may be output as part of the same deep network applied by the tracking system 140. Disparity images may be used for object detection separately from the images received from the image capture devices 114/115, or they may be combined into a single network for joint inference.

In general, a tracking system 140 (e.g., including an object detection system and/or an associated instance segmentation system) may be primary concerned with determining which pixels in a given image correspond to each object instance. However, these systems may not consider portions of a given object that are not actually captured in a given image. For example, pixels that would otherwise correspond with an occluded portion of an object (e.g., a person partially occluded by a tree) may not be labeled as corresponding to the object. This can be disadvantageous for object detection, instance segmentation, and/or identity recognition because the size and shape of the object may appear in the captured image to be distorted due to the occlusion. To address this issue, the tracking system 140 may be configured to imply a segmentation of an object instance in a captured image even if that object instance is occluded by other object instances. The object tracking system 140 may additionally be configured to determine which of the pixels associated with an object instance correspond with an occluded portion of that object instance. This process is generally referred to as “amodal segmentation” in that the segmentation process takes into consideration the whole of a physical object even if parts of the physical object are not necessarily perceived, for example, received images captured by the image capture devices 114/115. Amodal segmentation may be particularly advantageous when performing identity recognition and in a tracking system 140 configured for multi-object tracking.

Loss of visual contact is to be expected when tracking an object in motion through a physical environment. A tracking system 140 based primarily on visual inputs (e.g., images captured by image capture devices 114/115) may lose a track on an object when visual contact is lost (e.g., due to occlusion by another object or by the object leaving a FOV of an image capture device 114/115). In such cases, the tracking system 140 may become uncertain of the object's location and thereby declare the object lost. Human pilots generally do not have this issue, particularly in the case of momentary occlusions, due to the notion of object permanence. Object permanence assumes that, given certain physical constraints of matter, an object cannot suddenly disappear or instantly teleport to another location. Based on this assumption, if it is clear that all escape paths would have been clearly visible, then an object is likely to remain in an occluded volume. This situation is most clear when there is single occluding object (e.g., boulder) on flat ground with free space all around. If a tracked object in motion suddenly disappears in the captured image at a location of another object (e.g., the bolder), then it can be assumed that the object remains at a position occluded by the other object and that the tracked object will emerge along one of one or more possible escape paths. In some embodiments, the tracking system 140 may be configured to implement an algorithm that bounds the growth of uncertainty in the tracked objects location given this concept. In other words, when visual contact with a tracked object is lost at a particular position, the tracking system 140 can bound the uncertainty in the object's position to the last observed position and one or more possible escape paths given a last observed trajectory. A possible implementation of this concept may include generating, by the tracking system 140, an occupancy map that is carved out by stereo and the segmentations with a particle filter on possible escape paths.

Unmanned Aerial Vehicle—Example System

A UAV 100, according to the present teachings, may be implemented as any type of UAV. A UAV, sometimes referred to as a drone, is generally defined as any aircraft capable of controlled flight without a human pilot onboard. UAVs may be controlled autonomously by onboard computer processors or via remote control by a remotely located human pilot. Similar to an airplane, UAVs may utilize fixed aerodynamic surfaces along with a propulsion system (e.g., propeller, jet, etc.) to achieve lift. Alternatively, similar to helicopters, UAVs may directly use a propulsion system (e.g., propeller, jet, etc.) to counter gravitational forces and achieve lift. Propulsion-driven lift (as in the case of helicopters) offers significant advantages in certain implementations, for example, as a mobile filming platform, because it allows for controlled motion along all axes.

Multi-rotor helicopters, in particular quadcopters, have emerged as a popular UAV configuration. A quadcopter (also known as a quadrotor helicopter or quadrotor) is a multi-rotor helicopter that is lifted and propelled by four rotors. Unlike most helicopters, quadcopters use two sets of two fixed-pitch propellers. A first set of rotors turns clockwise, while a second set of rotors turns counter-clockwise. In turning opposite directions, a first set of rotors may counter the angular torque caused by the rotation of the other set, thereby stabilizing flight. Flight control is achieved through variation in the angular velocity of each of the four fixed-pitch rotors. By varying the angular velocity of each of the rotors, a quadcopter may perform precise adjustments in its position (e.g., adjustments in altitude and level flight left, right, forward and backward) and orientation, including pitch (rotation about a first lateral axis), roll (rotation about a second lateral axis), and yaw (rotation about a vertical axis). For example, if all four rotors are spinning (two clockwise, and two counter-clockwise) at the same angular velocity, the net aerodynamic torque about the vertical yaw axis is zero. Provided the four rotors spin at sufficient angular velocity to provide a vertical thrust equal to the force of gravity, the quadcopter can maintain a hover. An adjustment in yaw may be induced by varying the angular velocity of a subset of the four rotors thereby mismatching the cumulative aerodynamic torque of the four rotors. Similarly, an adjustment in pitch and/or roll may be induced by varying the angular velocity of a subset of the four rotors but in a balanced fashion such that lift is increased on one side of the craft and decreased on the other side of the craft. An adjustment in altitude from hover may be induced by applying a balanced variation in all four rotors, thereby increasing or decreasing the vertical thrust. Positional adjustments left, right, forward, and backward may be induced through combined pitch/roll maneuvers with balanced applied vertical thrust. For example, to move forward on a horizontal plane, the quadcopter would vary the angular velocity of a subset of its four rotors in order to perform a pitch forward maneuver. While pitching forward, the total vertical thrust may be increased by increasing the angular velocity of all the rotors. Due to the forward pitched orientation, the acceleration caused by the vertical thrust maneuver will have a horizontal component and will therefore accelerate the craft forward on a horizontal plane.

FIG. 38 shows a diagram of an example UAV system 3800 including various functional system components that may be part of a UAV 100, according to some embodiments. UAV system 3800 may include one or more means for propulsion (e.g., rotors 3802 and motor(s) 3804), one or more electronic speed controllers 3806, a flight controller 3808, a peripheral interface 3810, processor(s) 3812, a memory controller 3814, a memory 3816 (which may include one or more computer readable storage media), a power module 3818, a GPS module 3820, a communications interface 3822, audio circuitry 3824, an accelerometer 3826 (including subcomponents such as gyroscopes), an IMU 3828, a proximity sensor 3830, an optical sensor controller 3832 and associated optical sensor(s) 3834, a mobile device interface controller 3836 with associated interface device(s) 3838, and any other input controllers 3840 and input device(s) 3842, for example, display controllers with associated display device(s). These components may communicate over one or more communication buses or signal lines as represented by the arrows in FIG. 38 .

UAV system 3800 is only one example of a system that may be part of a UAV 100. A UAV 100 may include more or fewer components than shown in system 3800, may combine two or more components as functional units, or may have a different configuration or arrangement of the components. Some of the various components of system 3800 shown in FIG. 38 may be implemented in hardware, software or a combination of both hardware and software, including one or more signal processing and/or application specific integrated circuits. Also, UAV 100 may include an off-the-shelf UAV (e.g., a currently available remote-controlled quadcopter) coupled with a modular add-on device (for example, one including components within outline 3890) to perform the innovative functions described in this disclosure.

As described earlier, the means for propulsion 3802-3804 may comprise fixed-pitch rotors. The means for propulsion may also include variable-pitch rotors (for example, using a gimbal mechanism), a variable-pitch jet engine, or any other mode of propulsion having the effect of providing force. The means for propulsion 3802-3804 may include a means for varying the applied thrust, for example, via an electronic speed controller 3806 varying the speed of each fixed-pitch rotor.

Flight controller 3808 may include a combination of hardware and/or software configured to receive input data (e.g., sensor data from image capture devices 3834, and or generated trajectories form an autonomous navigation system 120), interpret the data and output control commands to the propulsion systems 3802-3806 and/or aerodynamic surfaces (e.g., fixed wing control surfaces) of the UAV 100. Alternatively, or in addition, a flight controller 3808 may be configured to receive control commands generated by another component or device (e.g., processors 3812 and/or a separate computing device), interpret those control commands and generate control signals to the propulsion systems 3802-3806 and/or aerodynamic surfaces (e.g., fixed wing control surfaces) of the UAV 100. In some embodiments, the previously mentioned navigation system 120 of the UAV 100 may comprise the flight controller 3808 and/or any one or more of the other components of system 3800. Alternatively, the flight controller 3808 shown in FIG. 38 may exist as a component separate from the navigation system 120, for example, similar to the flight controller 160 shown in FIG. 2 .

Memory 3816 may include high-speed random-access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 3816 by other components of system 3800, such as the processors 3812 and the peripherals interface 3810, may be controlled by the memory controller 3814.

The peripherals interface 3810 may couple the input and output peripherals of system 3800 to the processor(s) 3812 and memory 3816. The one or more processors 3812 run or execute various software programs and/or sets of instructions stored in memory 3816 to perform various functions for the UAV 100 and to process data. In some embodiments, processors 3812 may include general central processing units (CPUs), specialized processing units such as graphical processing units (GPUs) particularly suited to parallel processing applications, or any combination thereof. In some embodiments, the peripherals interface 3810, the processor(s) 3812, and the memory controller 3814 may be implemented on a single integrated chip. In some other embodiments, they may be implemented on separate chips.

The network communications interface 3822 may facilitate transmission and reception of communications signals often in the form of electromagnetic signals. The transmission and reception of electromagnetic communications signals may be carried out over physical media such as copper wire cabling or fiber optic cabling, or may be carried out wirelessly, for example, via a radiofrequency (RF) transceiver. In some embodiments, the network communications interface may include RF circuitry. In such embodiments, RF circuitry may convert electrical signals to/from electromagnetic signals and communicate with communications networks and other communications devices via the electromagnetic signals. The RF circuitry may include well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. The RF circuitry may facilitate transmission and receipt of data over communications networks (including public, private, local, and wide area). For example, communication may be over a wide area network (WAN), a local area network (LAN), or a network of networks such as the Internet. Communication may be facilitated over wired transmission media (e.g., via Ethernet) or wirelessly. Wireless communication may be over a wireless cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other modes of wireless communication. The wireless communication may use any of a plurality of communications standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11n and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, or any other suitable communication protocols.

The audio circuitry 3824, including the speaker and microphone 3850, may provide an audio interface between the surrounding environment and the UAV 100. The audio circuitry 3824 may receive audio data from the peripherals interface 3810, convert the audio data to an electrical signal, and transmit the electrical signal to the speaker 3850. The speaker 3850 may convert the electrical signal to human-audible sound waves. The audio circuitry 3824 may also receive electrical signals converted by the microphone 3850 from sound waves. The audio circuitry 3824 may convert the electrical signal to audio data and transmit the audio data to the peripherals interface 3810 for processing. Audio data may be retrieved from and/or transmitted to memory 3816 and/or the network communications interface 3822 by the peripherals interface 3810.

The I/O subsystem 3860 may couple input/output peripherals of UAV 100, such as an optical sensor system 3834, the mobile device interface 3838, and other input/control devices 3842, to the peripherals interface 3810. The I/O subsystem 3860 may include an optical sensor controller 3832, a mobile device interface controller 3836, and other input controller(s) 3840 for other input or control devices. The one or more input controllers 3840 receive/send electrical signals from/to other input or control devices 3842.

The other input/control devices 3842 may include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, touch screen displays, slider switches, joysticks, click wheels, and so forth. A touch screen display may be used to implement virtual or soft buttons and one or more soft keyboards. A touch-sensitive touch screen display may provide an input interface and an output interface between the UAV 100 and a user. A display controller may receive and/or send electrical signals from/to the touch screen. The touch screen may display visual output to a user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects, further details of which are described below.

A touch sensitive display system may have a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. The touch sensitive display system and the display controller (along with any associated modules and/or sets of instructions in memory 3816) may detect contact (and any movement or breaking of the contact) on the touch screen and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys or images) that are displayed on the touch screen. In an exemplary embodiment, a point of contact between a touch screen and the user corresponds to a finger of the user.

The touch screen may use liquid crystal display (LCD) technology, or light emitting polymer display (LPD) technology, although other display technologies may be used in other embodiments. The touch screen and the display controller may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with a touch screen.

The mobile device interface device 3838 along with mobile device interface controller 3836 may facilitate the transmission of data between a UAV 100 and other computing devices such as a mobile device 104. According to some embodiments, communications interface 3822 may facilitate the transmission of data between UAV 100 and a mobile device 104 (for example, where data is transferred over a Wi-Fi network).

UAV system 3800 also includes a power system 3818 for powering the various components. The power system 3818 may include a power management system, one or more power sources (e.g., battery, alternating current (AC), etc.), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in computerized device.

UAV system 3800 may also include one or more image capture devices 3834. Image capture devices 3834 may be the same as the image capture device 114/115 of UAV 100 described with respect to FIG. 1A. FIG. 38 shows an image capture device 3834 coupled to an image capture controller 3832 in I/O subsystem 3860. The image capture device 3834 may include one or more optical sensors. For example, image capture device 3834 may include a charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. The optical sensors of image capture devices 3834 receive light from the environment, projected through one or more lens (the combination of an optical sensor and lens can be referred to as a “camera”) and converts the light to data representing an image. In conjunction with an imaging module located in memory 3816, the image capture device 3834 may capture images (including still images and/or video). In some embodiments, an image capture device 3834 may include a single fixed camera. In other embodiments, an image capture device 3840 may include a single adjustable camera (adjustable using a gimbal mechanism with one or more axes of motion). In some embodiments, an image capture device 3834 may include a camera with a wide-angle lens providing a wider FOV. In some embodiments, an image capture device 3834 may include an array of multiple cameras providing up to a full 360 degree view in all directions. In some embodiments, an image capture device 3834 may include two or more cameras (of any type as described herein) placed next to each other in order to provide stereoscopic vision. In some embodiments, an image capture device 3834 may include multiple cameras of any combination as described above. In some embodiments, the cameras of an image capture device 3834 may be arranged such that at least two cameras are provided with overlapping FOV at multiple angles around the UAV 100, thereby allowing for stereoscopic (i.e., 3D) image/video capture and depth recovery (e.g., through computer vision algorithms) at multiple angles around UAV 100. For example, UAV 100 may include four sets of two cameras each positioned so as to provide a stereoscopic view at multiple angles around the UAV 100. In some embodiments, a UAV 100 may include some cameras dedicated for image capture of a subject and other cameras dedicated for image capture for visual navigation (e.g., through visual inertial odometry).

UAV system 3800 may also include one or more proximity sensors 3830. FIG. 38 shows a proximity sensor 3830 coupled to the peripherals interface 3810. Alternately, the proximity sensor 3830 may be coupled to an input controller 3840 in the I/O subsystem 3860. Proximity sensors 3830 may generally include remote sensing technology for proximity detection, range measurement, target identification, etc. For example, proximity sensors 3830 may include radar, sonar, and LIDAR.

UAV system 3800 may also include one or more accelerometers 3826. FIG. 38 shows an accelerometer 3826 coupled to the peripherals interface 3810. Alternately, the accelerometer 3826 may be coupled to an input controller 3840 in the I/O subsystem 3860.

UAV system 3800 may include one or more IMU 3828. An IMU 3828 may measure and report the UAV's velocity, acceleration, orientation, and gravitational forces using a combination of gyroscopes and accelerometers (e.g., accelerometer 3826).

UAV system 3800 may include a GPS receiver 3820. FIG. 38 shows an GPS receiver 3820 coupled to the peripherals interface 3810. Alternately, the GPS receiver 3820 may be coupled to an input controller 3840 in the I/O subsystem 3860. The GPS receiver 3820 may receive signals from GPS satellites in orbit around the earth, calculate a distance to each of the GPS satellites (through the use of GPS software), and thereby pinpoint a current global position of UAV 100.

In some embodiments, the software components stored in memory 3816 may include an operating system, a communication module (or set of instructions), a flight control module (or set of instructions), a localization module (or set of instructions), a computer vision module, a graphics module (or set of instructions), and other applications (or sets of instructions). For clarity, one or more modules and/or applications may not be shown in FIG. 38 .

An operating system (e.g., Darwin, RTXC, Linux, Unix, OS X, Windows, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

A communications module may facilitate communication with other devices over one or more external ports 3844 and may also include various software components for handling data transmission via the network communications interface 3822. The external port 3844 (e.g., Universal Serial Bus (USB), Firewire, etc.) may be adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.).

A graphics module may include various software components for processing, rendering and displaying graphics data. As used herein, the term “graphics” may include any object that can be displayed to a user, including, without limitation, text, still images, videos, animations, icons (such as user-interface objects including soft keys), and the like. The graphics module in conjunction with a graphics processing unit (GPU) 3812 may process in real time or near real time, graphics data captured by optical sensor(s) 3834 and/or proximity sensors 3830.

A computer vision module, which may be a component of a graphics module, provides analysis and recognition of graphics data. For example, while UAV 100 is in flight, the computer vision module along with a graphics module (if separate), processor 3812, and image capture devices(s) 3834 and/or proximity sensors 3830 may recognize and track the captured image of an object located on the ground. The computer vision module may further communicate with a localization/navigation module and flight control module to update a position and/or orientation of the UAV 100 and to provide course corrections to fly along a planned trajectory through a physical environment.

A localization/navigation module may determine the location and/or orientation of UAV 100 and provide this information for use in various modules and applications (e.g., to a flight control module in order to generate commands for use by the flight controller 3808).

Image capture devices(s) 3834, in conjunction with an image capture device controller 3832 and a graphics module, may be used to capture images (including still images and video) and store them into memory 3816.

Each of the above identified modules and applications correspond to a set of instructions for performing one or more functions described above. These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and, thus, various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 3816 may store a subset of the modules and data structures identified above. Furthermore, memory 3816 may store additional modules and data structures not described above.

Example Computer Processing System

FIG. 39 is a block diagram illustrating an example of a processing system 3900 in which at least some operations described in this disclosure can be implemented. The example processing system 3900 may be part of any of the aforementioned devices including, but not limited to UAV 100 and mobile device 104. The processing system 3900 may include one or more central processing units (“processors”) 3902, main memory 3906, non-volatile memory 3910, network adapter 3912 (e.g., network interfaces), display 3918, input/output devices 3920, control device 3922 (e.g., keyboard and pointing devices), drive unit 3924 including a storage medium 3926, and signal generation device 3930 that are communicatively connected to a bus 3916. The bus 3916 is illustrated as an abstraction that represents any one or more separate physical buses, point to point connections, or both connected by appropriate bridges, adapters, or controllers. The bus 3916, therefore, can include, for example, a system bus, a Peripheral Component Interconnect (PCI) bus or PCI-Express bus, a HyperTransport or industry standard architecture (ISA) bus, a small computer system interface (SCSI) bus, a universal serial bus (USB), IIC (I2C) bus, or an Institute of Electrical and Electronics Engineers (IEEE) standard 1394 bus (also called “Firewire”). A bus may also be responsible for relaying data packets (e.g., via full or half duplex wires) between components of the network appliance, such as the switching fabric, network port(s), tool port(s), etc.

In various embodiments, the processing system 3900 may be a server computer, a client computer, a personal computer (PC), a user device, a tablet PC, a laptop computer, a personal digital assistant (PDA), a cellular telephone, an iPhone, an iPad, a Blackberry, a processor, a telephone, a web appliance, a network router, switch or bridge, a console, a hand-held console, a (hand-held) gaming device, a music player, any portable, mobile, hand-held device, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by the computing system.

While the main memory 3906, non-volatile memory 3910, and storage medium 3926 (also called a “machine-readable medium”) are shown to be a single medium, the term “machine-readable medium” and “storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store one or more sets of instructions 3928. The term “machine-readable medium” and “storage medium” shall also be taken to include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by the computing system and that cause the computing system to perform any one or more of the methodologies of the presently disclosed embodiments.

In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module, or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions (e.g., instructions 3904, 3908, 3928) set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processing units or processors 3902, cause the processing system 3900 to perform operations to execute elements involving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readable media, or computer-readable (storage) media include recordable type media such as volatile and non-volatile memory devices 3910, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks (DVDs)), and transmission type media such as digital and analog communication links.

The network adapter 3912 enables the processing system 3900 to mediate data in a network 3914 with an entity that is external to the processing system 3900, such as a network appliance, through any known and/or convenient communications protocol supported by the processing system 3900 and the external entity. The network adapter 3912 can include one or more of a network adaptor card, a wireless network interface card, a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.

The network adapter 3912 can include a firewall which can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall may additionally manage and/or have access to an access control list which details permissions including, for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.

As indicated above, the techniques introduced here may be implemented by, for example, programmable circuitry (e.g., one or more microprocessors), programmed with software and/or firmware, entirely in special-purpose hardwired (i.e., non-programmable) circuitry, or in a combination or such forms. Special-purpose circuitry can be in the form of, for example, one or more application-specific integrated circuits (ASICs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), etc.

Note that any of the embodiments described above can be combined with another embodiment, except to the extent that it may be stated otherwise above or to the extent that any such embodiments might be mutually exclusive in function and/or structure.

Although the present invention has been described with reference to specific exemplary embodiments, it will be recognized that the invention is not limited to the embodiments described, but can be practiced with modification and alteration within the spirit and scope of the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative sense rather than a restrictive sense. 

1-30. (canceled)
 31. An aerial vehicle comprising: a sensor device configured to capture perception inputs of a physical environment; a propulsion system configured to maneuver the aerial vehicle through the physical environment; and a processing system configured to: expose, via an application programing interface (API), one or more parameters associated with a behavioral objective, wherein the behavioral objective is one of multiple behavioral objectives applied as part of a multi-objective trajectory generation process; adjust a first parameter of the one or more parameters associated with the behavioral objective based on a request received via the API; and process the perception inputs and one or more of the multiple behavioral objectives to generate a trajectory through the physical environment.
 32. The aerial vehicle of claim 31, wherein the processing system is configured to: direct the propulsion system to cause the aerial vehicle to autonomously maneuver the aerial vehicle along the trajectory through the physical environment.
 33. The aerial vehicle of claim 32, wherein the trajectory through the physical environment comprises a three-dimensional (3D) trajectory through the physical environment.
 34. The aerial vehicle of claim 31, wherein to process the perception inputs and the one or more of the multiple behavioral objectives to generate the trajectory through the physical environment, the processing system is configured to utilize a motion planner to execute a multi-objective trajectory generation process.
 35. The aerial vehicle of claim 34, wherein the multi-objective trajectory generation process generates and continually updates a three-dimensional (3D) trajectory through a physical environment surrounding the autonomous vehicle.
 36. The aerial vehicle of claim 31, wherein the request received via the API comprises an input from an application.
 37. The aerial vehicle of claim 36, wherein the processing system is configured to: expose, via the API, to the application, an output from a machine learning model that is generated by processing the perception inputs using the machine learning model; wherein the input from the application is based, at least in part, on the output from the machine learning model.
 38. The aerial vehicle of claim 37, wherein the machine learning model includes an artificial neural network.
 39. The aerial vehicle of claim 36, wherein the aerial vehicle further comprises: a wireless communication interface; wherein the processing system is configured to: download, via the wireless communication interface, from a remote computing platform a machine learning model, the machine learning model configured to the process perception inputs to generate model outputs; and expose, via the API, the model outputs to the application; wherein the input from the application is based, at least in part, on the model outputs.
 40. The aerial vehicle of claim 36, where the aerial vehicle further comprises: a wireless communication interface; wherein the computer system is configured to: download, via the wireless communication interface, from a remote computing platform, an update to the application.
 41. The aerial vehicle of claim 36, wherein the input is from a particular software module of multiple software modules associated with the application.
 42. The aerial vehicle of claim 41, wherein a developer of the particular software module is a third-party developer that did not develop the application.
 43. The aerial vehicle of claim 41, wherein the particular software module is extends functionality of the application.
 44. A computing apparatus comprising: one or more computer readable storage media; and program instructions stored on the one or more computer-readable storage media that, when executed by one or more processors of an aerial vehicle, direct the computing apparatus to at least: expose, via an application programing interface (API), one or more parameters associated with a behavioral objective, wherein the behavioral objective is one of multiple behavioral objectives applied as part of a multi-objective trajectory generation process; adjust a first parameter of the one or more parameters associated with the behavioral objective based on a request received via the API; process the perception inputs and one or more of the multiple behavioral objectives to generate a trajectory through the physical environment; and direct a propulsion system of the aerial vehicle to autonomously maneuver the aerial vehicle along the trajectory through the physical environment.
 45. The computing apparatus of claim 44, wherein the trajectory through the physical environment comprises a three-dimensional (3D) trajectory through the physical environment.
 46. The computing apparatus of claim 45, wherein to process the perception inputs and the one or more of the multiple behavioral objectives to generate the trajectory through the physical environment, the program instructions, when executed by the one or more processors of the aerial vehicle, direct the computing apparatus to utilize a motion planner to execute a multi-objective trajectory generation process.
 47. The computing apparatus of claim 46, wherein the multi-objective trajectory generation process generates and continually updates a three-dimensional (3D) trajectory through a physical environment surrounding the autonomous vehicle.
 48. The computing apparatus of claim 44, wherein the request received via the API comprises an input from an application, wherein the input is from a particular software module of multiple software modules associated with the application, and wherein the particular software module is extends functionality of the application.
 49. A method comprising: exposing, by a processing system of an aerial vehicle, via an application programing interface (API), one or more parameters associated with a behavioral objective, wherein the behavioral objective is one of multiple behavioral objectives applied as part of a multi-objective trajectory generation process; adjusting, by the processing system, a first parameter of the one or more parameters associated with the behavioral objective based on a request received via the API; processing, by the processing system, the perception inputs and one or more of the multiple behavioral objectives to generate a trajectory through the physical environment; and directing, by the processing system, a propulsion system of the aerial vehicle to autonomously maneuver the aerial vehicle along the trajectory through the physical environment.
 50. The method of claim 49, wherein the request received via the API comprises an input from an application, the method further comprising: exposing, by the processing system, via the API, to the application, an output from a machine learning model that is generated by processing the perception inputs using the machine learning model; wherein the input from the application is based, at least in part, on the output from the machine learning model. 